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/minicoohei/ai-agent-camp/setup-extensionsgit clone --depth 1 https://github.com/minicoohei/ai-agent-campWrote 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/minicoohei/ai-agent-camp/setup-extensions)<a href="https://agentmods.dev/commands/minicoohei/ai-agent-camp/setup-extensions"><img src="https://agentmods.dev/badge/commands/minicoohei/ai-agent-camp/setup-extensions.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.00002 | $0.03594 |
| Opus 5 | $0.00001 | $0.01797 |
| Sonnet 5 | $0.00000 | $0.00719 |
| Haiku 4.5 | $0.00000 | $0.00359 |
Grade A, and why
setup-extensions 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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 335 lines · 2 tokens per session scan A eeab4fccf89a
setup-extensions is a command published in the GitHub repository minicoohei/ai-agent-camp (348 stars, last pushed 4d ago), with no licence file. It adds 2 tokens to every session and 3,594 once invoked, about $0.0000 per session on Opus 5. 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
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
export-project
Export a single registered Gnosys project to a portable .json.gz bundle (round-trips with gnosys import project).
gaai-audit
Show workspace audit log with filters and optional JSON export.
make-this
Install the Multi-Agent Loop Kit into the current repo and run the setup interview.
rclone_config_dump
Dump the config file as JSON.
sync-validate
Validate Claude MCP schema and target capability compatibility before syncing.