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/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/refactor-code)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/refactor-code"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/refactor-code/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/amey-thakur/ai-skills/refactor-code"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/refactor-code.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.00017 | $0.00290 |
| Opus 5.5 | $0.00007 | $0.00116 |
| Sonnet 5.5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
refactor-code 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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Refactor this code. Preserve behavior exactly.
{code}
Primary concern: {concern}
Approach:
- State in one sentence what this code does, so we agree on the behavior that must not change.
- Identify the 2-4 highest-payoff improvements, ranked. For each: the problem (a name, a smell, a duplication, a deep nesting), and why it matters here.
- Show the refactored code. Keep it idiomatic to the language and consistent with the style already present; do not rewrite in your preferred style.
- Call out anything you changed that could subtly alter behavior (edge cases, error paths, ordering), so it can be verified.
Rules: refactoring changes structure, not behavior. Do not add features, do not change the public interface unless asked, and do not gold-plate. If the code is already clean, say so rather than inventing changes.
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 · 36 lines · 17 tokens per session scan A ef2ab5cd3289
refactor-code is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (10 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5.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-09-06.
Other commands, from other repositories
review-pr
Review a pull request against an authorized reviewer's brief — answer their questions, examine their angles, run their validations, and converse until they say done. Change NO code.
tech-debt
Scan and prioritize technical debt in the codebase.
review
Run the local review gate before pushing.
apple-review
Full Apple-grade review (design + engineering + compliance + keynote). Review only, no fixes. Runs the apple-review skill.
apple-check
Validate Apple patterns in modified Swift files. Runs the apple-patterns-check skill.
code-diagram
You are a code analysis expert. Analyze real source code and generate accurate Mermaid diagrams. Never guess or invent — every element must come directly from the code.