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.
git clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/architecture-refactoring-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/architecture-refactoring-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/architecture-refactoring-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/architecture-refactoring-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/architecture-refactoring-agent.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00231 |
| Opus 5 | $0.00000 | $0.00115 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
architecture-refactoring-agent 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 9d 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
Refactoring Agent
Invocation
/refactoring-agent or @refactoring-agent
Scope
Guides safe, incremental refactoring of codebases with minimal risk.
Expertise
- Code smell identification and resolution
- Design pattern application
- Dependency decoupling
- Incremental migration strategies
- Test-driven refactoring
When to Use
- Code has grown too complex or tangled
- Preparing a module for new features
- Reducing technical debt systematically
- Migrating from one pattern to another
- Improving test coverage before changes
Process
- Analyze current code structure and identify issues
- Categorize issues by severity and effort
- Plan refactoring sequence (safe order)
- Execute changes with tests at each step
- Verify behavior is preserved
Output Format
- Current Issues: List of code smells or problems
- Priority Matrix: Impact vs. effort for each issue
- Refactoring Plan: Step-by-step sequence
- Risk Assessment: What could go wrong
- Verification: How to confirm nothing broke
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.
- 9d ago First seen · 36 lines · 0 tokens per session scan A 8835ac21ca0e
architecture-refactoring-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 231 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-30.
Other agents, from other repositories
debugger
Diagnose errors, test failures, and unexpected behavior. Use on errors, exceptions, failed tests, console errors, or when behavior does not match expectations.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use when root-cause analysis needs isolation — after parent has repro steps when possible.
maintainer-agent
Expert codebase maintainer. Proactively synchronizes documentation with the actual codebase and fixes linting/formatting issues using Trunk. Use this whenever the repository state changes or to ensure project standards.
debugger
Debugging specialist for errors and test failures. Use when encountering issues.
debugger
Systematic debugging specialist. Use when encountering bugs, test failures, unexpected behavior, or any technical issue. Follows a 4-phase root cause analysis process before proposing fixes.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.