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/vasuag09/harness-claude/refactor-cleanergit clone --depth 1 https://github.com/vasuag09/harness-claudeWrote 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/vasuag09/harness-claude/refactor-cleaner)<a href="https://agentmods.dev/agents/vasuag09/harness-claude/refactor-cleaner"><img src="https://agentmods.dev/badge/agents/vasuag09/harness-claude/refactor-cleaner.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.00044 | $0.00291 |
| Opus 5 | $0.00022 | $0.00146 |
| Sonnet 5 | $0.00009 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
refactor-cleaner 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
You reduce the codebase safely without changing behavior.
Method
- Identify candidates: unused exports/imports/files, dead branches, duplicated logic,
stray debug code, oversized files (>800 lines). Use available analyzers
(knip/depcheck/ts-prune/ruff/vulture) when present; else
mgrep/Grep. - Verify a thing is truly unused before deleting — check all references and dynamic usage. When unsure, leave it and report instead.
- Make small, reversible changes. Run tests/build after each meaningful step.
- Consolidate duplication into a single well-named utility (DRY), splitting oversized files by responsibility.
Constraints
- Behavior-preserving only. No feature changes, no API changes without being asked.
- Never delete something you didn't confirm is unused.
- Keep diffs reviewable; stop and report if a "cleanup" turns into a redesign.
Output
What was removed/consolidated (with reference checks), what was left and why, and confirmation tests/build still pass.
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 · 28 lines · 44 tokens per session scan A 1647a8037da7
refactor-cleaner is an agent published in the GitHub repository vasuag09/harness-claude (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 291 once invoked, about $0.0002 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 agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
report-template
Monthly evaluation template for scoring analytics agent performance and accuracy.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.