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/sd0xdev/sd0x-harness/doc-refactorgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWhat 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.00022 | $0.00341 |
| Opus 5 | $0.00011 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
doc-refactor 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
Doc Refactor
Goal
Refactor verbose documents into:
- Concise content (reduce context usage)
- No information loss (preserve key details)
- Visual flows (use Mermaid)
Refactoring Principles
sequenceDiagram
participant D as Doc
participant R as Refactor
participant O as Output
D->>R: Original document
R->>R: Identify core information
R->>R: Remove redundancy
R->>R: Tabulate comparisons
R->>R: Convert to flowcharts
R-->>O: Condensed document
Techniques
| Before | After |
|---|---|
| Long paragraphs | Table comparison |
| Step-by-step lists | sequenceDiagram |
| Repeated information | Single source + reference |
| Too many examples | 1 key example |
Size Standards
- CLAUDE.md: < 50 lines
- rules/*.md: < 30 lines
- agents/*.md: < 50 lines
- commands/*.md: < 40 lines
Output
## Refactoring Summary
- Original lines: X
- After condensing: Y
- Reduction: Z%
## Major Changes
- <what was removed/consolidated>
Constraints
- No deleting key information
- No changing document purpose
- Prefer tables and flowcharts
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 · 67 lines · 22 tokens per session scan A 2a0071523fd6
doc-refactor is an agent published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 341 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-30.
Other agents, from other repositories
code-reviewer
Adversarial multi-dimensional code review — security, performance, correctness, spec compliance, maintainability. Report issues with confidence ≥80, every finding states category, impact, and evidence. Runs after component-builder in BUILD workflows.
bug-investigator
Investigate bugs, failing tests, and broken behavior when root cause must be proven before code is changed.
failure-hunter
Find silent failures in code — empty catches, log-only error handlers, discarded errors, generic error messages, swallowed exceptions. Zero tolerance for error handling that hides bugs. Runs in parallel with code-reviewer during BUILD workflows.
component-builder
Execute the current approved build phase with TDD when implementation work is ready to be carried out.
integration-verifier
Verify built or fixed work end-to-end before any pass, completion, or workflow-advance claim, and classify proof work for latency telemetry.
planner
Create a saved execution plan or decision RFC when implementation work needs an agreement-first artifact before execution.