Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-cli/main/.claude/commands/refactor.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/refactor)<a href="https://agentmods.dev/commands/namastexlabs/automagik-cli/refactor"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-cli/refactor.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.00000 | $0.03602 |
| Opus 5 | $0.00000 | $0.01801 |
| Sonnet 5 | $0.00000 | $0.00720 |
| Haiku 4.5 | $0.00000 | $0.00360 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/refactor
allowed-tools: Task(), Read(), Write(), Edit(), MultiEdit(), Glob(), Grep(*), Bash(find *), Bash(wc *), Bash(head *), Bash(tail *), Bash(sort *), Bash(uniq *), Bash(cat ), Bash(grep ), Bash(ls ), Bash(tree ), mcp__zen__refactor(), mcp__zen__analyze(), mcp__search-repo-docs__, mcp__ask-repo-agent__ description: Intelligent code refactoring with comprehensive analysis and safety validation
You are working on the PagBank Multi-Agent System project. The user has requested to refactor specific files tagged with @ symbols in their arguments: "$ARGUMENTS"
Live Refactoring Intelligence
- Project size: !
find . -name "*.py" | wc -lPython files, !find . -name "*.md" | wc -ldocs - Code complexity: !
find . -name "*.py" -exec wc -l {} + | sort -nr | head -10 - Import patterns: !
grep -r "^from\|^import" --include="*.py" . | wc -limport statements - Large files: !
find . -name "*.py" -exec wc -l {} + | awk '$1 > 200 {print $2 " (" $1 " lines)"}' | head -10 - Agent structure: !
find agents/ -name "*.py" | head -10agent files - Team structure: !
find teams/ -name "*.py" | head -5team files - Circular imports: !
grep -r "from agents" agents/ | grep -v __pycache__ | wc -lpotential circulars - Configuration files: !
find . -name "*.yaml" -o -name "*.json" | wc -lconfig files - Code smells: !
grep -r "TODO\|FIXME\|XXX\|HACK" --include="*.py" . | wc -ltechnical debt - Function distribution: !
grep -r "def " --include="*.py" . | wc -ltotal functions - Class distribution: !
grep -r "class " --include="*.py" . | wc -ltotal classes
Usage Examples
# Refactor specific agent files
/refactor "@agents/pagbank/agent.py is too complex, split into smaller modules"
# Refactor team structure
/refactor "@teams/ana/team.py has too many responsibilities, extract routing logic"
# Refactor configuration management
/refactor "@context/knowledge/knowledge_base.py needs better organization"
# Multi-file refactoring
/refactor "@agents/registry.py and @agents/base.py need better separation of concerns"
# Business logic refactoring
/refactor "@workflows/typification/ needs modular structure for easier testing"
# Pattern-based refactoring
/refactor "Extract common patterns from @agents/ directory and reduce duplication"
# Performance refactoring
/refactor "Optimize database queries in @db/queries.py for better performance"
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.
- 3d ago First seen · 334 lines · 0 tokens per session scan A ba7e22117bae
refactor is a command published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,602 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-09-04.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.