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/nickpolyder/np.copilot.config/implementation-runnernpx skills add NickPolyder/NP.CoPilot.Config --skill implementation-runnergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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.00031 | $0.00992 |
| Opus 5 | $0.00015 | $0.00496 |
| Sonnet 5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
implementation-runner 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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Execute an approved
tasks.mdin dependency order, producing working code with tests and updated task status. Always: follow task order; respect dependencies; write tests alongside code; update completed tasks; report after each phase and final verification. Never: skip ahead, ignore failing tests, or change approved scope silently.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
You are executing an approved task breakdown, keeping implementation, tests, and task status synchronized.
Your goals are to:
- Implement in order — respect dependencies and do not skip ahead.
- Test alongside code — add or update tests with each implementation task.
- Maintain status — mark completed tasks in
tasks.mdas work is verified. - Report progress — summarize each phase, test results, and any deviations from the design.
When to use this skill
Use this skill whenever:
- A
tasks.mdhas been approved and implementation should begin. - The user asks to execute an existing task breakdown in order.
- Work needs task status updates, per-phase reporting, and test verification.
- You need the fourth atomic step in the chain:
codebase-research→feature-design-doc→task-breakdown→implementation-runner.
Do not use this skill for:
- Initial research — use
codebase-research. - Writing a design document — use
feature-design-doc. - Creating the task breakdown — use
task-breakdown. - Commit review or commit creation — prepare a handoff and recommend
git-commit-review.
Workflow
Execute tasks in order, producing working code with tests.
- Follow task order — respect dependencies. Do not skip ahead.
- For each task:
- Implement the code change.
- Write unit tests alongside the code.
- Mark the task as complete in
tasks.md(prefix with[x]).
- After each phase (group of related tasks), report:
- What was implemented.
- Test results (pass/fail counts).
- Any deviations from the design.
- After all tasks are complete, run the full test suite and report results.
- Commit handoff — after implementation is verified, delegate commit review and commit creation to
git-commit-review.
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.
- yesterday First seen · 107 lines · 31 tokens per session scan A cdb70056113f
implementation-runner is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 992 once invoked, about $0.0002 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…