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/callgit 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.01331 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
call scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
It's the equivalent of `curl` with credential injection handled by the keychain rather than the shell. How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentsecrets call
Make a single authenticated API call without exposing credentials.
Usage
agentsecrets call --url <URL> [options]
Description
agentsecrets call is a one-shot proxy command. It resolves the specified secret from the OS keychain, injects it into the outbound HTTP request at the transport layer, makes the request, and returns the API response — without the secret value ever appearing in your terminal, in a log, or in agent context.
It's the equivalent of curl with credential injection handled by the keychain rather than the shell.
Options
| Flag | Description |
|---|---|
--url |
Required. Target API URL |
--method |
HTTP method (default: GET) |
--body |
Request body (string, typically JSON) |
--bearer KEY |
Inject secret as Authorization: Bearer <value> |
--basic KEY |
Inject secret as Authorization: Basic base64(<value>) — format: user:pass |
--header X-Name=KEY |
Inject secret as custom header X-Name: <value> |
--query param=KEY |
Inject secret as URL query param ?param=<value> |
--body-field path=KEY |
Set secret at JSON body path (dot notation for nesting) |
--form-field field=KEY |
Set secret in form-encoded body |
Multiple injection flags can be combined in a single call.
Examples
Bearer token (most common)
agentsecrets call --url https://api.stripe.com/v1/balance --bearer STRIPE_KEY
agentsecrets call --url https://api.openai.com/v1/models --bearer OPENAI_KEY
POST with body
agentsecrets call \
--url https://api.stripe.com/v1/charges \
--method POST \
--bearer STRIPE_KEY \
--body '{"amount": 1000, "currency": "usd", "source": "tok_visa"}'
Custom header (API key in header)
agentsecrets call \
--url https://api.sendgrid.com/v3/mail/send \
--method POST \
--header X-Api-Key=SENDGRID_KEY \
--body '{"personalizations":[...]}'
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 · 174 lines · 0 tokens per session scan A 7df06cd11522
call 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,331 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.