DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to compute a TOTP code locally for an account's second factor with Skills

An agent stores a TOTP secret beside its API key and computes six-digit codes on the machine per RFC 6238.

Short answer: Store the TOTP secret for the account in the agent environment next to SVN_API_KEY, not in the repo; then use a local RFC 6238 TOTP library or script to compute the six-digit code from the stored secret; Enter the computed code within its validity window when the account asks for the authenticator step. All steps.

Authorization notice. Skills is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. A TOTP secret is equivalent to the second factor itself, so anyone who reads it can log into the account; store it with the same care as a password.

Who it is forAn operator whose agent-run account asks for an authenticator app code after the phone step and who wants the agent to finish that step without a human.

The problemAfter the SMS code, many accounts ask for a time-based one-time password that the agent cannot produce from a phone number alone.

The outcomeThe agent computes the current six-digit TOTP code on the local machine and enters it, so the secret never leaves the machine.

What you need first

  • An SV Number account with a funded balance, since the README says there is no free tier
  • An API key from your SV Number profile, exported as SVN_API_KEY
  • curl and jq, plus Python or Node.js if you run the bundled scripts
  • An agent runner that reads Agent Skills, such as Claude Code or Codex

Steps

  1. Store the TOTP secret for the account in the agent environment next to SVN_API_KEY, not in the repo.
  2. Use a local RFC 6238 TOTP library or script to compute the six-digit code from the stored secret. (inferred, check the README)
  3. Enter the computed code within its validity window when the account asks for the authenticator step.
  4. Confirm the account accepts the code and record that the secret stayed on the machine.

Prompt for your agent

Using the sv-number skill from the sv-number-skills repo, store the TOTP secret for <account name> in the local environment and compute the current six-digit code per RFC 6238. Expected output: a six-digit code accepted by the account. Verify that the secret was not sent to any remote service before you report the code.

Caveat. The README describes the TOTP step as part of this skill but does not show the code or library for it, so the exact implementation is left to you.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for sv-number/skills and "Compute a TOTP code locally for an account's second factor"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer