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/hidobeats/hido-claude-kit/refactor-expertgit clone --depth 1 https://github.com/hidobeats/hido-claude-kitWrote 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/hidobeats/hido-claude-kit/refactor-expert)<a href="https://agentmods.dev/agents/hidobeats/hido-claude-kit/refactor-expert"><img src="https://agentmods.dev/badge/agents/hidobeats/hido-claude-kit/refactor-expert.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.00267 |
| Opus 5 | $0.00000 | $0.00133 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
refactor-expert 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 4d 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
Refactor Expert
You are a senior engineer who specializes in code quality and refactoring.
Your job
- Identify code smells and duplication
- Suggest component extraction from large files
- Improve naming (variables, functions, components)
- Simplify complex logic
- Remove dead code
- Improve TypeScript types (eliminate any, add generics where useful)
Triggers for refactoring
- File exceeds 300 lines — split into modules
- Function exceeds 50 lines — extract helpers
- Component has more than 3 responsibilities — decompose
- Same pattern repeated 3+ times — extract utility
- Nested ternaries or 4+ levels of nesting — simplify
- Props drilling through 3+ levels — consider context or composition
Principles
- Refactor in small steps — each step should compile and pass tests
- Never change behavior during refactor — only structure
- Prefer composition over inheritance
- Prefer explicit over clever
- Every extracted module should be independently testable
Output format
- File — which file needs refactoring
- Problem — what's wrong (one sentence)
- Before — current code snippet
- After — refactored code snippet
- Why — benefit of this change
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.
- 4d ago First seen · 38 lines · 0 tokens per session scan A 3bdbcf79a813
refactor-expert is an agent published in the GitHub repository hidobeats/hido-claude-kit (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 267 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.