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/vinilana/dotcontext/feature-breakdownnpx skills add vinilana/dotcontext --skill feature-breakdowngit clone --depth 1 https://github.com/vinilana/dotcontextWrote 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/vinilana/dotcontext/feature-breakdown)<a href="https://agentmods.dev/skills/vinilana/dotcontext/feature-breakdown"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/feature-breakdown.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.01513 |
| Opus 5 | $0.00005 | $0.00757 |
| Sonnet 5 | $0.00002 | $0.00303 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
Feature Breakdown 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 4d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Breakdown
Break down features into concrete, implementable tasks within the @dotcontext/cli architecture.
When to Use
- Starting the Planning (P) phase of a PREVC workflow
- Scoping a new CLI command, MCP tool, or service
- Creating a plan document in
.context/plans/ - Estimating complexity to choose the right workflow scale (QUICK/SMALL/MEDIUM/LARGE)
Instructions
1. Classify the Feature Scope
Determine which layers of the codebase are involved:
| Layer | Directory | Examples |
|---|---|---|
| CLI | src/index.ts |
New command, new flag, output format change |
| Service | src/services/<domain>/ |
New business logic, data processing |
| Generator | src/generators/ |
New scaffold type, template changes |
| MCP | src/services/mcp/ |
New tool, new gateway action, schema change |
| Workflow | src/workflow/ |
Phase logic, gate rules, skill/agent integration |
| Utils | src/utils/ |
New utility function, i18n keys, CLI UI changes |
| Types | src/types/, src/types.ts |
New interfaces, frontmatter types |
2. Determine the Workflow Scale
Use these criteria to set the scale when calling workflow-init:
| Scale | Criteria | Typical Feature |
|---|---|---|
| QUICK | Single file, no design decisions | Fix typo, update translation key |
| SMALL | 2-5 files, straightforward logic | Add a flag to existing CLI command |
| MEDIUM | Multiple services, design decisions needed | New MCP gateway action with service |
| LARGE | New subsystem, cross-cutting concerns | New generator type, new AI provider |
3. Identify the Task Breakdown Pattern
Most features in this project follow one of these patterns:
Pattern A: New MCP Gateway Action
- Define the action in the Zod schema (
mcpServer.ts) - Add handler logic in the gateway file (
src/services/mcp/gateway/<tool>.ts) - Create or extend the backing service (
src/services/<domain>/) - Update type exports in
gatewayTools.tsandgateway/index.ts - Add tests for the handler
- Update MCP tool description string
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.
- 4d ago First seen · 166 lines · 10 tokens per session scan A 8eeef78263fd
Feature Breakdown is a skill published in the GitHub repository vinilana/dotcontext (564 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 1,513 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…