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/samibs/skillfoundry/improvegit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/improve)<a href="https://agentmods.dev/commands/samibs/skillfoundry/improve"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/improve.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.03197 |
| Opus 5 | $0.00000 | $0.01598 |
| Sonnet 5 | $0.00000 | $0.00639 |
| Haiku 4.5 | $0.00000 | $0.00320 |
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 yesterday.
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 — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/improve — Continuous Improvement Loop
Scans the codebase for improvement opportunities, fixes them one at a time, and loops until no improvements remain or the token budget is exhausted.
This is Boris Cherny's "agent prompting itself" pattern applied to codebase health: the agent scans → prioritizes → fixes → checkpoints → scans again. No human input between iterations.
Protocol engine:
agents/_ralph-loop-protocol.md+agents/_self-prompt-protocol.md
Usage
/improve Scan and fix all improvement categories
/improve arch Architectural improvements only
/improve duplication Duplicate code / abstraction consolidation
/improve quality Code quality (GuardLoop patterns GL-01 through GL-10)
/improve security Security posture improvements
/improve --dry-run Show what would be fixed, do not apply any changes
/improve --resume Resume a previously interrupted improvement loop
/improve --budget [N] Set max iterations (default: 10)
/improve --pr Open a PR with all fixes when the loop completes
What This Command Does
This is a self-prompting loop — the agent finds the work, does the work, finds more work, and stops when there is nothing left.
LOOP {
1. SCAN — Identify all improvement opportunities in scope
2. PRIORITIZE — Rank by impact, select the single highest-priority item
3. FIX — Apply the fix (surgical — one item per iteration, no scope creep)
4. VERIFY — Confirm the fix did not regress anything
5. CHECKPOINT — Record: what was fixed, what remains, what was learned
6. JUDGE — Any improvements remaining? Budget sufficient to continue?
7. SELF-PROMPT — Formulate: "I fixed X. Still need to address Y at [location]."
8. → RE-ENTER at step 2 with that self-prompt as current_task
}
EXIT when:
- Backlog is empty (no improvements remain in scope)
- Token budget < 20% remaining
- Max iterations reached
- Same item appears in remaining work twice with no change (oscillation)
- An item cannot be fixed without user input (blocked)
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.
- yesterday First seen · 388 lines · 0 tokens per session scan A 704d319c493c
improve is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,197 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.