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 feature-planninggit 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/feature-planning)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/feature-planning"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/feature-planning/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/feature-planning"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/feature-planning.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.00040 | $0.03027 |
| Opus 5.5 | $0.00016 | $0.01211 |
| Sonnet 5.5 | $0.00008 | $0.00605 |
| Haiku 4.5 | $0.00004 | $0.00303 |
Grade A, and why
feature-planning 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 — 415 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 conducting a comprehensive feature planning process.
The phase labels describe perspectives, not mandatory agents. Use investigator
only for substantial unresolved analysis; proposed approved implementation uses
implementer with a domain focus. Do not implement during this planning workflow.
Your goals are to:
- Gather and clarify requirements from a product perspective.
- Assess UX needs — user flows, wireframe considerations, and usability.
- Evaluate architectural impact — how the feature fits into the system.
- Plan implementation — what needs to be built, by whom, in what order.
- Define test strategy — what to test and how.
- Identify security considerations — threats and mitigations.
- Plan deployment — infrastructure needs and rollout strategy.
- Produce a comprehensive feature plan that the team can execute against.
When to use this skill
Use this skill whenever:
- A new feature needs to be planned from scratch.
- The user asks to "plan a feature", "scope out", or "design" a significant piece of work.
- A feature spans multiple domains (frontend, backend, database, infrastructure).
- The team needs a shared understanding of what will be built and how.
Do not use this skill for:
- Simple tasks that don't need multi-agent planning.
- Bug fixes (just fix them).
- Pure architecture decisions (use the
architecture-decision-recordskill). - Pure requirement breakdowns without technical planning (use the
requirement-breakdownskill).
Choosing between
feature-planningandprd-workflow: Usefeature-planningwhen you need a comprehensive plan document only — no implementation. Useprd-workflowwhen you intend to plan AND implement a feature end-to-end.
Boundary: This skill may summarize requirements, test, security, and ADR needs, but it recommends
requirement-breakdown,test-strategy,security-audit, orarchitecture-decision-recordwhen those areas need their full dedicated workflows.
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 9db74771f406
- 1mo ago First seen · 422 lines · 40 tokens per session scan A 2ff2ce0423c7
feature-planning is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 3,027 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…