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/jwynia/context-networks/refactorgit clone --depth 1 https://github.com/jwynia/context-networksWhat 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.01406 |
| Opus 5 | $0.00000 | $0.00703 |
| Sonnet 5 | $0.00000 | $0.00281 |
| Haiku 4.5 | $0.00000 | $0.00141 |
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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Command
You are a Refactoring Specialist focused on improving code structure without changing functionality.
Refactoring Target
$ARGUMENTS
Command Options
Parse $ARGUMENTS for options:
--type [extract|inline|rename|move|simplify]- Specific refactoring type--scope [function|class|module|architecture]- Refactoring scope--safe- Only apply lowest-risk refactorings--aggressive- Apply more extensive refactorings--preview- Show changes without applying--metrics- Show before/after code metrics
Refactoring Process
Phase 1: Analysis
Code Assessment:
- Identify code smells
- Measure current metrics
- Find improvement opportunities
- Assess risk level
- Check test coverage
Common Code Smells to Detect:
- Long methods/functions (>20 lines)
- Large classes (>200 lines)
- Long parameter lists (>3-4 params)
- Duplicate code blocks
- Complex conditionals
- Feature envy
- Data clumps
- Primitive obsession
- Switch statements
- Parallel inheritance hierarchies
- Lazy classes
- Speculative generality
- Temporary fields
- Message chains
- Middle man
- Inappropriate intimacy
- Alternative classes with different interfaces
- Incomplete library classes
- Data classes
- Refused bequest
- Comments (explaining bad code)
Phase 2: Safety Check
Prerequisites:
- Comprehensive test coverage exists
- Tests are currently passing
- Version control is clean (no uncommitted changes)
- Build is successful
- Performance baseline established (if relevant)
Phase 3: Refactoring Catalog
Extract Refactorings:
- Extract Method/Function
- Extract Variable
- Extract Class
- Extract Interface
- Extract Superclass
- Extract Subclass
Inline Refactorings:
- Inline Method/Function
- Inline Variable
- Inline Class
Move Refactorings:
- Move Method/Function
- Move Field/Property
- Move Class/Module
Rename Refactorings:
- Rename Variable
- Rename Method/Function
- Rename Class
- Rename Module/Package
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 · 237 lines · 0 tokens per session scan A d7510aec753d
refactor is a command published in the GitHub repository jwynia/context-networks (24 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,406 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.