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/Justdvp/claude-code-templatesWrote 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/commands/justdvp/claude-code-templates/refactor)<a href="https://agentmods.dev/commands/justdvp/claude-code-templates/refactor"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/refactor/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/commands/justdvp/claude-code-templates/refactor"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/refactor.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.00335 |
| Opus 5.5 | $0.00000 | $0.00134 |
| Sonnet 5.5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- refactor — 100% identical, 0 lines differ
What it actually says
Code Refactoring Assistant
Refactor $ARGUMENTS following modern JavaScript/TypeScript best practices.
Task
I'll help you refactor code by:
- Analyzing the current implementation
- Identifying improvement opportunities
- Applying modern patterns and practices
- Maintaining existing functionality
- Ensuring type safety and test coverage
- Documenting the changes made
Process
I'll follow these steps:
- Examine the code to understand its purpose and structure
- Identify code smells, anti-patterns, or outdated approaches
- Plan the refactoring strategy with clear goals
- Implement changes incrementally while maintaining behavior
- Verify refactored code with tests
- Document improvements and benefits
Refactoring Techniques
I can apply various refactoring techniques:
- Converting to modern JavaScript/TypeScript features
- Improving type definitions and type safety
- Extracting reusable functions and components
- Applying design patterns appropriately
- Converting callbacks to Promises or async/await
- Simplifying complex conditionals and loops
- Removing duplicate code
- Improving naming and readability
- Optimizing performance
- Enhancing error handling
Modern Practices I Can Apply
- ES modules and import/export syntax
- Optional chaining and nullish coalescing
- Array and object destructuring
- Spread and rest operators
- Template literals
- Arrow functions
- Class fields and private methods
- TypeScript utility types
- Functional programming patterns
- React hooks (for React components)
I'll ensure the refactored code maintains compatibility with your project's requirements while improving quality and maintainability.
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A 760bb38335cb
refactor is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 335 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 commands, from other repositories
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.
migrate-pipeline
Migrate an existing pre-v2 per-tier pipeline (.claude/, .opencode/, .agents/codex/) into the unified data-only .superpipelines/ layout — select legacy pipeline, translate frontmatter to canonical agent defs, stage, delta-audit, gate on human approval, then atomically promote, rewrite the registry, and move the legacy…
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
new-pipeline
Design and scaffold a new named multi-agent pipeline with git preflight, scope selection, pre-gate audit, and entry-skill generation.
optimize-pipeline
Optimize an existing pipeline on demand — survey topology, model-tier cost, and past-run signals, lock an optimization plan with the user, then batch-apply it atomically with a mandatory post-apply audit.