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/execgit clone --depth 1 https://github.com/The-17/agentsecretsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/the-17/agentsecrets/exec)<a href="https://agentmods.dev/commands/the-17/agentsecrets/exec"><img src="https://agentmods.dev/badge/commands/the-17/agentsecrets/exec.svg" alt="Measured on agentmods" height="20"></a>What 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.00172 |
| Opus 5 | $0.00000 | $0.00086 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
exec 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 today.
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 exec
Inject decrypted secrets directly into child process memory without creating unencrypted
.envfiles.
Usage
agentsecrets exec -- <command> [args...]
The -- separator is required. Everything following -- is executed with secrets resolved in process address space.
Examples
# Node.js
agentsecrets exec -- npm run dev
# Python
agentsecrets exec -- python manage.py runserver
# Go
agentsecrets exec -- go run ./cmd/server
For full details and comparison with proxy injection, visit: 👉 Process Execution (exec) Guide 👉 Environment Injection Overview
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.
- today First seen · 30 lines · 0 tokens per session scan A 6bedb676ce75
exec is a command published in the GitHub repository The-17/agentsecrets (172 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 172 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-09-03.
Other commands, from other repositories
nyxid-connect
Connect a catalog service through NyxID without placing its credential in the agent context.
git
Git operations with intelligent commit messages and workflow optimization.
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.