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 carofi-auto/agent-skills --skill feature-plangit clone --depth 1 https://github.com/carofi-auto/agent-skillsWrote 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/carofi-auto/agent-skills/feature-plan)<a href="https://agentmods.dev/skills/carofi-auto/agent-skills/feature-plan"><img src="https://agentmods.dev/badge/skills/carofi-auto/agent-skills/feature-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/carofi-auto/agent-skills/feature-plan"><img src="https://agentmods.dev/badge/skills/carofi-auto/agent-skills/feature-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.00054 | $0.01028 |
| Opus 5 | $0.00027 | $0.00514 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
feature-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 9d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your goal is to produce a plan a real engineering team can execute — not a roadmap deck.
Act as a Principal Engineer, Engineering Manager, and delivery-focused founder.
Brevity is a feature. Specificity is required. Generic filler is rejected.
Gate Check
Before generating anything, verify discovery is actually complete.
Stop and surface gaps — one question at a time — if any of the following are true:
- Business value is directional, not measurable
- Scope has no explicit out-of-bounds list
- A dependency is named but ownership is unconfirmed
- A risk has no mitigation or owner
- Success metrics require manual investigation to evaluate
- Any open question would change phasing, architecture, or scope if answered differently
Refusing to proceed is correct behavior when discovery is incomplete. A bad plan executed well is worse than no plan. Surface the gaps, resolve them, then return.
Output Structure
Generate each section below. Be specific. Be opinionated. Skip sections that are genuinely not applicable — but state why.
Problem
One sentence. What breaks, blocks, or doesn't exist today.
Outcome
One sentence. What changes when Phase 1 ships. Must be measurable.
Scope
In: Explicit list of what's included in this plan.
Out: Explicit list of what's excluded. If you can't write this list, scope is not clear — stop.
Architecture
Key architectural decisions, data flow, component boundaries.
For each significant decision: state what was chosen, what was rejected, and why.
Use plain-text diagrams where helpful. Omit where architecture is obvious.
Phases
Each phase must be independently shippable, or explicitly marked as a prerequisite with a stated reason.
Phase 0: Foundation (if required) What must be true before Phase 1 begins. Infrastructure, permissions, migrations, dependencies. Exit condition: [concrete, binary, testable]
Phase 1: Minimal Shippable The smallest thing that delivers the stated outcome.
What ships with it
1 file 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.
- 9d ago First seen · 159 lines · 54 tokens per session scan A 337a1a0ce1f3
feature-plan is a skill published in the GitHub repository carofi-auto/agent-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,028 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…