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 implementation-runnergit 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/implementation-runner)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/implementation-runner"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/implementation-runner/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/implementation-runner"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/implementation-runner.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.00031 | $0.00983 |
| Opus 5.5 | $0.00012 | $0.00393 |
| Sonnet 5.5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
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 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 — 108 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 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.
- Keep applicable tests with changed behavior using the repository's runner; record no-runner limits and any policy-permitted direct verification.
- Verify the task before marking it complete in
tasks.md(prefix with[x]).
- After each phase (group of related tasks), report:
- What was implemented.
- Revision-bound verification (commands, working directories, pass/fail/skip
counts or explicit no-runner limits; never invented
0/0passes). - Any deviations from the design.
- Final verification — run the repository-required final checks, including the full existing test suite when applicable. Follow the shared no-runner contract; missing required checks remain blockers.
- Commit handoff — return completion and evidence to the invoking workflow
(such as
prd-workflow); this phase finishing does not end its parent. Standalone, finish this skill before recommending a separategit-commit-review. Never start it inside an active parent.
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 · +1 lines 6592e38e95f0
- 1mo ago 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 1mo ago), licensed MIT. It adds 31 tokens to every session and 983 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…