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/phuoctrung-ppt/ai-sdlc-workflow/planningnpx skills add phuoctrung-ppt/ai-sdlc-workflow --skill planninggit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/phuoctrung-ppt/ai-sdlc-workflow/planning)<a href="https://agentmods.dev/skills/phuoctrung-ppt/ai-sdlc-workflow/planning"><img src="https://agentmods.dev/badge/skills/phuoctrung-ppt/ai-sdlc-workflow/planning.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.1 | $0.00020 | $0.01184 |
| Opus 5 | $0.00010 | $0.00592 |
| Sonnet 5 | $0.00004 | $0.00237 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade A, and why
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 5d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning
Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
When to Use
Use this skill when:
- Planning new feature implementations
- Architecting system designs
- Evaluating technical approaches
- Creating implementation roadmaps
- Breaking down complex requirements
- Assessing technical trade-offs
Core Responsibilities & Rules
Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
1. Codebase Understanding
Load: references/codebase-understanding.md
Skip if: Provided with codebase or architecture exiting
2. Planning on a lower-capability model
Load: references/planning-with-lower-models.md
Load when: running on a small/cheap model, or when plans come out vague,
truncated, or full of placeholders. It grounds the model in real facts, forces
one-section-at-a-time output, and adds a self-verify gate.
Workflow Process
- Initial Analysis → Read
docs/architecture.md+.cursor/rules/*.mdcfor the real stack/structure (AGENTS.md §2/§3 may be blank template — do not plan from blanks). Read 1–3 similar existing files. - Research Phase → Investigate approaches yourself; if the task is large, delegate targeted lookups via the Task tool (
generalPurpose). This roster has no standalone "researcher" agent — do not invent one. - Synthesis → Analyze findings, identify optimal solution
- Design Phase → Create architecture, implementation design
- Plan Documentation → Fill the architect-planner Plan Template field-by-field (do not restructure it)
- Review & Refine → Run the self-verify gate (see
references/planning-with-lower-models.md§2 Rule 5) before handoff
Output Requirements
- DO NOT implement code - only create plans (and sync domain config docs)
- Respond with plan file path and summary
- Ensure self-contained plans with necessary context
- Include code snippets/pseudocode when clarifying
- Provide multiple options with trade-offs when appropriate
- Fully respect the
./docs/development-rules.mdfile.
What ships with it
4 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.
- 5d ago First seen · 121 lines · 20 tokens per session scan A 6849144455b7
planning is a skill published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 19d ago), licensed MIT. It adds 20 tokens to every session and 1,184 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-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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…