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/envgit 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.02226 |
| Opus 5 | $0.00000 | $0.01113 |
| Sonnet 5 | $0.00000 | $0.00445 |
| Haiku 4.5 | $0.00000 | $0.00223 |
Grade A, and why
env 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentsecrets env
Inject secrets from the OS keychain as environment variables into a child process.
Usage
agentsecrets env -- <command> [args...]
The -- separator is required. Everything after it is passed verbatim as the command and its arguments.
Makefile Integration
The lowest-friction way to use agentsecrets env in a project is to define a RUN variable at the top of your Makefile and prefix commands with it. This way you type make dev and not agentsecrets env -- npm run dev.
Pattern 1: RUN prefix variable (recommended)
Define once, use everywhere:
RUN := agentsecrets env --
dev:
$(RUN) npm run dev
test:
$(RUN) npm test
migrate:
$(RUN) python manage.py migrate
server:
$(RUN) python manage.py runserver
worker:
$(RUN) celery -A myapp worker --loglevel=info
build:
$(RUN) go build ./...
Now make dev runs with secrets injected. The RUN variable acts as a transparent prefix.
Bonus: You can override RUN from the shell to strip injection entirely (useful for debugging without the keychain):
make dev RUN= # runs: npm run dev (no injection)
make dev # runs: agentsecrets env -- npm run dev
Pattern 2: Named targets (explicit)
If you prefer each target to be completely self-contained:
dev:
agentsecrets env -- npm run dev
test:
agentsecrets env -- pytest
migrate:
agentsecrets env -- python manage.py migrate
shell:
agentsecrets env -- python manage.py shell
Django project example (full Makefile)
RUN := agentsecrets env --
.PHONY: dev test migrate shell celery
dev:
$(RUN) python manage.py runserver
test:
$(RUN) python manage.py test
migrate:
$(RUN) python manage.py migrate
shell:
$(RUN) python manage.py shell
celery:
$(RUN) celery -A myapp worker --loglevel=info
# Run without injection (for debugging env setup)
dev-raw:
python manage.py runserver
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 · 324 lines · 0 tokens per session scan A 244dde63b018
env 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 2,226 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.