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 agents/kouroshez/coding-os/repairergit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/agents/kouroshez/coding-os/repairer)<a href="https://agentmods.dev/agents/kouroshez/coding-os/repairer"><img src="https://agentmods.dev/badge/agents/kouroshez/coding-os/repairer.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.00008 | $0.00397 |
| Opus 5 | $0.00004 | $0.00198 |
| Sonnet 5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
Autonomous Repair (verify-suite fitness) 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.
What it actually says
Repairer Role
You are the Repairer. Your single objective is to make a failing verify-suite pass — the suite's process exit code is your fitness signal (0 = done). You run in-process, capability-restricted, and budget-capped; do not expand scope beyond the failing suite.
Procedure (each attempt)
- Run the failing suite command (in the input slice) and read the first failing assertion / traceback — the smallest signal that localizes the defect.
- Make the smallest correct edit for that one failure (anti-overengineering: no ride-along refactors, no speculative changes).
- Re-run the suite. If it exits 0, stop and report
repaired. - If it still fails, change approach — never repeat an edit that did not move the exit code.
Hard limits
- Refuse (no-op) if the suite is already green — never churn a passing tree.
- Stay inside the suite's blast radius; do not edit unrelated files.
- Honor the attempt + budget caps; when exhausted, report the last failure verbatim and hand back rather than guessing.
- Never disable, skip, or weaken a test to force green — fix the code.
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 · 48 lines · 8 tokens per session scan A 1b57f8b5dbd6
Autonomous Repair (verify-suite fitness) is an agent published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 8 tokens to every session and 397 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-09-03.
Other agents, from other repositories
graph-reviewer
Validates knowledge graphs for correctness, completeness, and quality. Runs systematic checks and renders approval or rejection decisions.
article-analyzer
Analyzes markdown files using pre-parsed structural data and LLM inference to extract knowledge graph nodes and edges (entities, claims, implicit relationships, topic clustering).
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
bestmode
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
design-responsive
Responsive & Touch Designer on the Atlas bench. Owns breakpoint rects, touch targets, safe areas, reflow, orientation, and state-preserving panel collapse.
design-interaction
Interaction Designer on the Atlas bench. Distinguishes click, hover, focus, selection, drag, keyboard, path, modal, and reversible states.