Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/the-17/agentsecrets/secretsgit clone --depth 1 https://github.com/The-17/agentsecretsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01025 |
| Opus 5 | $0.00000 | $0.00513 |
| Sonnet 5 | $0.00000 | $0.00205 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
secrets scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentsecrets secrets
Manage secrets for the active project — store, sync, and inspect credentials.
Subcommands
agentsecrets secrets list
agentsecrets secrets set <KEY=value> [KEY=value...]
agentsecrets secrets delete <KEY>
agentsecrets secrets pull [--force]
agentsecrets secrets push
agentsecrets secrets diff
agentsecrets secrets list
List all secret key names for the active project.
agentsecrets secrets list
agentsecrets secrets list --project my-other-app
Returns key names only — values are never decrypted or displayed. The list is fetched from the API and compared against what's in the local keychain.
STRIPE_KEY
OPENAI_KEY
DATABASE_URL
SENDGRID_KEY
agentsecrets secrets set
Store or update a secret. The value is encrypted client-side before being sent to the server.
agentsecrets secrets set STRIPE_KEY=sk_live_51H... DATABASE_URL=postgresql://user:pass@host:5432/db
What happens:
- Retrieves the workspace key from
~/.agentsecrets/config.json - Encrypts the value with AES-256-GCM:
ciphertext = AES-GCM(workspace_key, nonce, value) - Sends
{key, ciphertext+nonce}to the API — server stores the blob - If StorageMode is Keychain, also writes the value to the OS keychain
The API only ever receives and stores the ciphertext. It cannot decrypt.
Naming Conventions
Use UPPER_SNAKE_CASE. Common patterns:
# API keys
STRIPE_KEY
OPENAI_KEY
GITHUB_TOKEN
SENDGRID_KEY
# Database
DATABASE_URL
REDIS_URL
# Application
DJANGO_SECRET_KEY
JWT_SECRET
SESSION_SECRET
# Service accounts
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
GCP_SERVICE_ACCOUNT_JSON
agentsecrets secrets push
Encrypt all secrets from the current source (keychain or .env file) and upload them to the project.
agentsecrets secrets push
StorageMode 1 (Keychain): Reads all keys from the OS keychain and pushes them.
StorageMode 0 (Standard): Reads your .env file and pushes all entries.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 170 lines · 0 tokens per session scan A 195c4574df2d
secrets is a command published in the GitHub repository The-17/agentsecrets (172 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,025 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
nyxid-connect
Connect a catalog service through NyxID without placing its credential in the agent context.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.