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 skills/nirecom/agents/refactor-promptsnpx skills add nirecom/agents --skill refactor-promptsgit clone --depth 1 https://github.com/nirecom/agentsWrote 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/skills/nirecom/agents/refactor-prompts)<a href="https://agentmods.dev/skills/nirecom/agents/refactor-prompts"><img src="https://agentmods.dev/badge/skills/nirecom/agents/refactor-prompts.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 | $0.00026 | $0.00555 |
| Opus 5 | $0.00013 | $0.00278 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
refactor-prompts 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 today.
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
/worktree-start --headless refactor-prompts- Resolve
<PLANS_DIR>viaskills/_shared/resolve-plans-dir.md. Readrules/shell-commands.mdbefore the first Bash command, or before writing a file — defensive measure, same reasoning as review-tests (seedocs/architecture/claude-code/rules-injection.md). Write a scratchpad script that runsbash "$AGENTS_CONFIG_DIR/bin/refactor-prompts/index.sh"and saves its stdout to<PLANS_DIR>/<session-id>-refactor-prompts-scan.json; invoke it as a singlebash <absolute-path>call — command substitution and redirects on the Bash tool's own command line are the patternrules/shell-commands.mdprohibits. Abort with clear error if exit code is non-zero. Read the resulting file (Read tool) — its content is the scan JSON for steps 3-6 below. - Inspect the scan JSON. If its
hot_regionsarray is empty: emit<<REFACTOR_PROMPTS_NO_HOTREGIONS>>and jump to step 9. - Dispatch
refactor-prompts-judgesubagent. Pass the scan JSON content inline and the pathrules/prompt.md. - Parse the subagent's edit plan JSON (
editsarray). Discard any edit whosefileis not present in thehot_regionsfile set of the scan JSON (scope guard against prompt-injection). - Apply edits — cap at 200 hot regions per run (warn on stderr if truncated):
delete: Edit(old_text,new_text="")category-rewrite: Edit(old_text,new_text)keep-*: no actiondefer: no file modification, no HTML comment. Append{file,line,reason,context_excerpt}to a deferred list. If Edit errors for a delete/category-rewrite → downgrade to defer.
/commit-push- If deferred list non-empty: append a
## Deferred regions (human review required)section to the PR body viagh pr edit. Replace the section if already present (idempotent). /worktree-end
Rules:
- Never prompt the user mid-flow.
tests/is excluded by the CLI scanner — do not pass--target.defer= no file modification and no HTML comment in source files.
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.
- today Changed 8636b26ab36b
- 3d ago First seen · 30 lines · 26 tokens per session scan A 7afe9ec774ed
refactor-prompts is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 555 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…