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/agoldian/claudenv/improvegit clone --depth 1 https://github.com/AGoldian/claudenvWhat 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.00019 | $0.00459 |
| Opus 5 | $0.00010 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
improve 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.
What it actually says
/improve — Single Improvement Iteration
You are an expert software engineer. Your job is to analyze this project and make one high-impact improvement.
Step 1: Read Context
Read these files if they exist:
CLAUDE.md— project overview and conventions_state.md— session memory.claude/improvement-plan.md— existing improvement plan (if any)
Step 2: Choose What to Improve
If .claude/improvement-plan.md exists:
- Read the plan and pick the top unfinished item from the "## Pending" section
- If
$ARGUMENTSis provided, use it as a focus area instead of the plan
If no plan exists:
- Analyze the project: read manifest files, scan source code, check test coverage
- If
$ARGUMENTSis provided, focus on that area - Identify the single highest-impact improvement you can make
Step 3: Implement the Change
- Write the code changes
- Add or update tests if applicable
- Follow existing code style and conventions
Step 4: Verify
- Run tests (if a test command is available)
- Run linter (if configured)
- Fix any issues found
Step 5: Update Plan
If .claude/improvement-plan.md exists:
- Move the completed item from "## Pending" to "## Completed"
- Add the commit hash and notes about what was done
- If you discovered new issues, add them to "## Pending"
Step 6: Commit and Report
- Commit all changes with a descriptive message
- Report:
- What you changed and why
- What tests were added/updated
- What's next (remaining plan items or suggested improvements)
Important Rules
- Do NOT delete files unless the deletion IS the improvement
- Make exactly ONE improvement per invocation
- If there's nothing left to improve, output: NO_MORE_IMPROVEMENTS
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 · 61 lines · 19 tokens per session scan A 3e9faddf2923
improve is a command published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 459 once invoked, about $0.0001 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-31.