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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/refactor)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/refactor"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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/boparaiamrit/skills-by-amrit/refactor"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.00014 | $0.00381 |
| Opus 5 | $0.00007 | $0.00191 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 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
/refactor — Safe Refactoring
Refactor code while maintaining correctness through continuous verification.
Instructions
-
Assess the target from
$ARGUMENTS:- Read and understand the current code
- Identify code smells: duplication, long functions, god classes, deep nesting
- Map all callers and dependents of the code being refactored
-
Establish a safety net:
- Run existing tests:
npm test/pytest/ etc. - If no tests exist → WRITE CHARACTERIZATION TESTS FIRST
- Note the current test results as the baseline
- Run existing tests:
-
Plan the refactoring — choose from:
- Extract function — pull logic into a named function
- Extract class — separate responsibilities
- Rename — improve naming for clarity
- Move — relocate code to better module
- Inline — remove unnecessary abstraction
- Replace conditional with polymorphism
- Introduce parameter object — group related params
-
Execute in small steps:
- Make ONE refactoring move at a time
- Run tests after EACH move
- If tests fail → revert and try a different approach
- Commit after each successful step
-
Verify the refactoring:
- All existing tests still pass
- No new warnings or errors
- Code is measurably simpler (fewer lines, less nesting, better names)
- All callers still work correctly
-
NEVER combine refactoring with behavior changes — do one or the other.
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 · 46 lines · 14 tokens per session scan A 2d6085107ebf
refactor is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 381 once invoked, about $0.0001 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.