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 prd-workflowgit 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/prd-workflow)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/prd-workflow"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/prd-workflow/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/prd-workflow"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/prd-workflow.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.00045 | $0.01251 |
| Opus 5.5 | $0.00018 | $0.00500 |
| Sonnet 5.5 | $0.00009 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
prd-workflow 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 — 130 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.
This skill is a thin orchestrator. It owns the end-to-end design-first flow and the approval gates between phases, but delegates each phase's detailed procedure to a dedicated atomic skill:
codebase-research— read-only investigation producing a grounded research summary.feature-design-doc—design.mdgrounded in that research.task-breakdown—tasks.mdderived from the design.implementation-runner— code + tests executed in task order.
For single-phase needs, invoke those skills directly. Use this orchestrator when you intend to plan and implement a feature end-to-end.
When to use this skill
Use this skill whenever:
- A new feature or project needs end-to-end planning and implementation.
- The user asks to "build", "create", or "develop" something from scratch.
- The user wants a structured design-first workflow rather than ad-hoc coding.
Do not use this skill for:
- Quick bug fixes or small tweaks — just code those directly.
- Pure exploration or research — invoke
codebase-researchdirectly. - Modifying existing design/task documents — edit them directly.
Choosing between
prd-workflowandfeature-planning: Useprd-workflowwhen you intend to plan AND implement a feature end-to-end. Usefeature-planningwhen you need a comprehensive plan document only — no implementation.
Boundary: This workflow sequences only its four phase skills. Return deep test/security needs as recommendations for separate work. Finish this entry workflow's own state before any
git-commit-review,test-strategy, orsecurity-audithandoff; a completed phase does not by itself end this workflow or waive another workflow's approval gates.
Workflow
Execute these phases in strict order, delegating each to its atomic skill. Do not advance to the next phase without user approval.
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 · -7 lines 829b8a1541d1
- 1mo ago First seen · 137 lines · 45 tokens per session scan A 6b29fd3c2644
prd-workflow is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,251 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
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,"…