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-biomechanist/windows-dev-agent/defraggit clone --depth 1 https://github.com/The-Biomechanist/Windows-Dev-AgentWrote 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/the-biomechanist/windows-dev-agent/defrag)<a href="https://agentmods.dev/commands/the-biomechanist/windows-dev-agent/defrag"><img src="https://agentmods.dev/badge/commands/the-biomechanist/windows-dev-agent/defrag.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.1 | $0.00018 | $0.00081 |
| Opus 5 | $0.00009 | $0.00041 |
| Sonnet 5 | $0.00004 | $0.00016 |
| Haiku 4.5 | $0.00002 | $0.00008 |
Grade A, and why
defrag 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.
What it actually says
Use the bundled windows-dev-agent:ecosystem-defrag skill as the canonical procedure for this command.
Treat any $ARGUMENTS as additional scope or constraints. Do not duplicate or weaken the skill's inventory, overlap, authority, rollback, or verification rules in the command adapter.
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 · 8 lines · 18 tokens per session scan A e1110ad93a3b
defrag is a command published in the GitHub repository The-Biomechanist/Windows-Dev-Agent (0 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 81 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.
Other commands, from other repositories
fixlinks
Find replacement URLs for broken links using research agents.
rotatechangelog
Archive current changelog and start fresh.
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
check-env
Check that the fenced React Native session, Metro, app target, and device inventory are ready for testing.