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 commands/alphaaiservice/cortex/refactorgit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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.00050 | $0.07914 |
| Opus 5 | $0.00025 | $0.03957 |
| Sonnet 5 | $0.00010 | $0.01583 |
| Haiku 4.5 | $0.00005 | $0.00791 |
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 yesterday.
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 — 841 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Powered Code Refactoring
Refactor target: $ARGUMENTS
Parse $ARGUMENTS to extract:
- target: file path or directory path (required)
- --type: refactoring focus —
extract,decompose,rename,cleanup, orall(default:all) - --yes: skip confirmation prompt and apply all recommended refactorings automatically
- --dry-run: analyze and plan only, do not apply any changes
- --aggressive: lower thresholds (functions >30 lines, files >300 lines, nesting >3)
- --conservative: raise thresholds (functions >80 lines, files >800 lines, nesting >5)
If no target is provided, default to the current working directory.
Step 0: Safety — Worktree Isolation (MANDATORY before any mutation)
📖 CANONICAL REFERENCE:
commands/references/WORKTREE_SAFETY.mddefines the safety decision tree for all file-mutation commands. Load it and follow it BEFORE anyWrite/Edit/Bashmutation in this run.
Quick summary (full tree + rationale in the reference file):
- Confirm scope with the user, then ask: isolated worktree (DEFAULT, recommended) vs current checkout (risky, requires opt-in) vs cancel.
- Isolated worktree (default): either spawn the mutation phase as
Agent({ ..., isolation: "worktree" }), OR manuallygit worktree add ../<repo>-refactor-$(date +%s) -b refactor/auto. After completion, show the diff and let the user merge / cherry-pick / discard. - Current checkout (only with explicit user opt-in): refuse if
git status --porcelainis non-empty; create a savepoint commit before any mutation so rollback isgit reset --hard HEAD~1. - No git: refuse to proceed.
Never start mutating files before completing this decision tree.
Step 0.5: Pre-Flight Validation
Before doing anything, validate the environment:
# Verify target exists
ls -la $TARGET 2>/dev/null || echo "ERROR: Target not found"
# Detect project language(s)
# Python: look for .py files, pyproject.toml, requirements.txt
# TypeScript: look for .ts/.tsx files, tsconfig.json, package.json
# JavaScript: look for .js/.jsx files, package.json
# Go: look for .go files, go.mod
# Rust: look for .rs files, Cargo.toml
# Check for git — we need it for safe rollback
git status 2>/dev/null || echo "WARNING: Not a git repo — no rollback safety net"
# Stash any uncommitted changes if present (safety)
git stash list 2>/dev/null
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.
- yesterday First seen · 841 lines · 50 tokens per session scan A 613821f21b87
refactor is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 50 tokens to every session and 7,914 once invoked, about $0.0003 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 commands, from other repositories
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
alfred
Asistente contextual de Alfred Dev. Enruta automáticamente al flujo o comando operativo correcto.
audit
Auditoría completa del proyecto con 4 agentes en paralelo.
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
ajustes
Configura Alfred Dev: autonomía, proyecto, Lucius, memoria y personalidad. Antes /alfred-dev:config.
discuss
Refina una idea o feature antes de abrir un flujo completo de implementación.