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 ABilenduke/copilot-developer --skill plangit clone --depth 1 https://github.com/ABilenduke/copilot-developerWrote 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/abilenduke/copilot-developer/plan)<a href="https://agentmods.dev/skills/abilenduke/copilot-developer/plan"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/plan/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/abilenduke/copilot-developer/plan"><img src="https://agentmods.dev/badge/skills/abilenduke/copilot-developer/plan.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.00111 | $0.05140 |
| Opus 5.5 | $0.00044 | $0.02056 |
| Sonnet 5.5 | $0.00022 | $0.01028 |
| Haiku 4.5 | $0.00011 | $0.00514 |
Grade A, and why
plan 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 — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Planner Skill
⛔ HARD RULES — READ BEFORE DOING ANYTHING
These rules are absolute. No exceptions. No workarounds.
Rule 1: NEVER create features
You do NOT create feature directories, feature READMEs, or update the feature index. EVER.
If the user names a feature that does not exist under docs/features/, STOP and tell them: "The feature '{name}' doesn't exist in the catalog. Please run /feature to create it first, then come back to /plan."
Feature creation belongs to /feature. Not you. Not ever.
Rule 2: ALWAYS use the story directory structure
Plans go here and ONLY here:
docs/features/{feature}/stories/{YYYY-MM-DD}_{story-name}/plan.md
CORRECT:
docs/features/auth/stories/2026-02-21_add-oauth2/plan.md
WRONG — all of these are WRONG:
docs/features/auth/plan.md
docs/features/auth/stories/plan.md
docs/plans/auth-add-oauth2.md
Format detection: If the user points you at an existing directory under iterations/, use the old monolithic format (backward compatibility). If creating new work, always use stories/.
Rule 3: NEVER skip the done gate
Each document layer has a done gate. Do not write the file until the gate criteria are met through the interactive process.
Verification Checklist (run before Phase 1)
-
docs/features/exists? If no → STOP, tell user to run/feature - Target feature directory exists? If no → STOP, tell user to run
/feature - Story directory exists or can be created at
docs/features/{feature}/stories/{YYYY-MM-DD}_{story-name}/? - All checks pass? → Proceed
Purpose
This skill enforces a planning-first discipline for software development. Before any code is written, you walk the developer through an interactive 7-phase discovery process that produces four altitude-layered documents:
| Document | Question | Phase(s) | Mutable? |
|---|---|---|---|
brief.md |
WHY are we doing this? | Phase 1 | Immutable after approval |
prd.md |
WHAT are we building? | Phases 2 + 6 | Immutable after approval |
design.md |
HOW will we build it? | Phases 3-5 | Immutable after approval |
plan.md |
WHEN and in what ORDER? | Phase 7 | Immutable after approval |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 544 lines · 111 tokens per session scan A edc7396f3f8a
plan is a skill published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 5,140 once invoked, about $0.0004 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…