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/proxygit 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.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
proxy 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 yesterday.
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.
What it actually says
agentsecrets proxy
Manage local zero-knowledge proxy workflows for your AI agents.
Usage
agentsecrets proxy <command> [flags]
Description
The proxy commands manage the runtime connection between an AI agent and your APIs. It securely resolves keys from the OS keychain, intercepts outbound agent requests in real-time, applies zero-trust domain authorizations, and injects authentication headers without exposing values to the agent model.
Available Commands
start
Starts the HTTP credential proxy on your local machine (default port 8765).
agentsecrets proxy start [--port 9000]
status
Displays the running status of your HTTP proxy, its uptime, process ID, the most recent background sync interval, and the volume of active/revoked identities that have been cached.
agentsecrets proxy status
sync
Forces an immediate cryptographic revocation sync. If a teammate compromised or revoked a key globally, this instantly blocks your proxy from making outbound calls with it. Note that the proxy already auto-syncs periodically every 10 seconds.
agentsecrets proxy sync
logs
Streams or views your proxy's local execution audit trail. This log structure definitively details memory-safe API interactions without displaying any raw secret content.
agentsecrets proxy logs # view entire log history
agentsecrets proxy logs --watch # stream log outputs in real time
agentsecrets proxy logs --last N # show last N entries
agentsecrets proxy logs --secret <key> # filter logs associated to a local key
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.
- yesterday First seen · 47 lines · 0 tokens per session scan A af3b169ce824
proxy is a command published in the GitHub repository The-17/agentsecrets (172 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 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.