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/inadarei/claude-code-interactive-mode/instrument-projectgit clone --depth 1 https://github.com/inadarei/claude-code-interactive-modeWrote 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/inadarei/claude-code-interactive-mode/instrument-project)<a href="https://agentmods.dev/commands/inadarei/claude-code-interactive-mode/instrument-project"><img src="https://agentmods.dev/badge/commands/inadarei/claude-code-interactive-mode/instrument-project.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.00276 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade B, and why
instrument-project scanned grade B 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
4. Copy `~/.claude/settings.local.json` to `./.claude/settings.json` — skip if `./.claude/settings.json` already exists What it actually says
Initialize this project with my standard Claude configuration files.
- Run
mkdir -p .claude{commands,hooks}to create the.claude/commandsand.claude/hooksdirectories if they doesn't exist - Copy
~/.claude/CLAUDE.mdto./CLAUDE.md— skip if./CLAUDE.mdalready exists - Copy
~/.claude/hooks/check-context-doc.shto.claude/hooks/check-context-doc.sh- skip if it already exists - Copy
~/.claude/settings.local.jsonto./.claude/settings.json— skip if./.claude/settings.jsonalready exists - Copy
~/.claude/commands/instrument-project.mdto./.claude/commands/instrument-project.md— skip if./.claude/commands/instrument-project.mdalready exists - Copy
~/.claude/commands/document-context.mdto./.claude/commands/document-context.md— skip if./.claude/commands/document-context.mdalready exists - Add
~/.claude/.gitignorefile with a single entry ofsettings.local.json - Report each file: whether it was copied or skipped (already exists)
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.
- 4d ago First seen · 11 lines · 0 tokens per session scan B 0a5e7d0200e4
instrument-project is a command published in the GitHub repository inadarei/claude-code-interactive-mode (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 276 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
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.