Borrowing it
Nothing to install: this file belongs to rmjosea/agentic-sdlc-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rmjosea/agentic-sdlc-kit/main/.agents/skills/plan/SKILL.mdgit clone --depth 1 https://github.com/rmjosea/agentic-sdlc-kitWrote 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/rmjosea/agentic-sdlc-kit/plan)<a href="https://agentmods.dev/skills/rmjosea/agentic-sdlc-kit/plan"><img src="https://agentmods.dev/badge/skills/rmjosea/agentic-sdlc-kit/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/rmjosea/agentic-sdlc-kit/plan"><img src="https://agentmods.dev/badge/skills/rmjosea/agentic-sdlc-kit/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.00095 | $0.00611 |
| Opus 5.5 | $0.00038 | $0.00244 |
| Sonnet 5.5 | $0.00019 | $0.00122 |
| Haiku 4.5 | $0.00010 | $0.00061 |
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 2mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan an Implementation
Convert approved product behavior into a technically coherent design. Do not modify production code.
Discover
- Read only the authoritative source intent and relevant repository guidance.
- Inspect the codebase, tests, dependencies, and established conventions.
- Identify constraints, reusable components, trust boundaries, and unknowns.
- Separate repository facts, confirmed constraints, assumptions, and choices.
Resolve decisions conversationally
For every material uncertainty, apply the human decision protocol in
AGENTS.md:
- ask one clear, self-contained question at a time;
- offer distinct alternatives with consequences;
- mark and justify the recommended option;
- update the confirmed design after each answer.
Ask when a choice materially affects architecture, data, APIs, security, cost, operability, compatibility, reversibility, or task structure. Decide trivial, reversible, repository-standard details directly and record the rationale.
Do not write the final plan until material decisions are resolved and the user has confirmed the proposed technical direction.
Design
Cover only what the change needs:
- components and responsibilities;
- interfaces and integration points;
- data ownership, model, and migration;
- security and privacy boundaries;
- failure handling and recovery;
- compatibility and rollout;
- observability;
- verification strategy.
Create a separate technical artifact only when several tasks share it, it needs
independent review, or moving it out materially reduces task context. Possible
artifacts include architecture.md, data-model.md, api-contract.md,
migration.md, and test-strategy.md.
Use assets/plan.template.md and write temporary
planning artifacts under .work/<feature>/. Keep the plan draft while a
material decision or user confirmation is pending; set it to approved only
after the user confirms the complete technical direction.
Quality gate
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.
- 2mo ago First seen · 73 lines · 95 tokens per session scan A ae7783447dc7
plan is a skill published in the GitHub repository rmjosea/agentic-sdlc-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 611 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…