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 skills add NickPolyder/NP.CoPilot.Config --skill refactorgit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWrote 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/nickpolyder/np.copilot.config/refactor)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/refactor"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/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/skills/nickpolyder/np.copilot.config/refactor"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/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.00043 | $0.01713 |
| Opus 5.5 | $0.00017 | $0.00685 |
| Sonnet 5.5 | $0.00009 | $0.00343 |
| Haiku 4.5 | $0.00004 | $0.00171 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are executing a disciplined refactoring process with evidence-based safety checks.
Your goals are to:
- Preserve behavior — refactoring changes structure, not behavior.
- Verify continuously — all required tests and agreed verification checks must pass after every atomic step; missing coverage remains explicit.
- Work incrementally — small, reversible changes, not big-bang rewrites.
- Prepare clean commit-review handoff — when refactoring is verified, recommend
git-commit-reviewrather than owning commit strategy.
When to use this skill
Use this skill whenever:
- Restructuring code without changing its behavior (rename, extract, move, inline, etc.).
- The user asks to "refactor", "clean up", "reorganize", or "restructure" code.
- Preparatory refactoring before a feature (making the codebase ready for a change).
- Reducing technical debt in a specific area.
Do not use this skill for:
- Adding new features or behavior — that's implementation, not refactoring.
- Bug fixes that change behavior — fix the bug directly.
- Simple renames with no structural impact — do them directly.
Workflow
Phase 1: Establish Baseline
Before touching anything:
- Run the existing test baseline — use the repository-required scope and record pass/fail counts and unavailable checks. This is your safety net.
- If tests are failing — HARD STOP. Do not refactor against a broken baseline. Report the failures and do not proceed until the baseline is fixed outside this refactoring.
- Identify the refactoring scope — which files, classes, or modules are affected?
- Check for coverage — map executed tests to the changed behaviors and record measured coverage, untested paths, and missing measurements. Passing tests or a coverage percentage do not establish that all behavior is covered.
- Bind the evidence — record baseline revision, command, working directory,
scope, result, and skips. If no applicable runner exists, report that fact,
not a passing
0/0suite; do not proceed without a policy-permitted, explicitly agreed verification alternative and its limitations.
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 Changed · +21 lines · +1 tokens per session d61b3b4638f5
- 1mo ago First seen · 161 lines · 42 tokens per session scan A b96ac17f0549
refactor is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,713 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…