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/srstomp/pokayokay/planningnpx skills add srstomp/pokayokay --skill planninggit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/planning)<a href="https://agentmods.dev/skills/srstomp/pokayokay/planning"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/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 | $0.00042 | $0.00819 |
| Opus 5 | $0.00021 | $0.00409 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Analyzer & Implementation Planner
Transform product requirements into actionable implementation plans with visual kanban tracking.
When NOT to Use
- Revising an existing plan — Use
plan-revisionfor modifying task hierarchies or scope changes - Starting implementation — Use
work-sessionto begin executing tasks from a plan - Quick one-off tasks — Use
/quickfor tasks that don't need epic/story/task hierarchy - Investigating feasibility — Use
spikefor time-boxed technical investigation before committing to a plan
Key Principles
- Plan state lives in ohno (
.ohno/, epics → stories → tasks managed via MCP tools/CLI);.claude/PROJECT.mdholds the project overview - Break work into epic → story → task hierarchy (tasks ≤ 8h each)
- Assign skills to features based on type (api-design, database-design, etc.)
- Flag ambiguities before planning — don't assume unclear requirements
Quick Start Checklist
- Read the full PRD/brief document
- Extract goals, features, constraints, and dependencies
- Classify priorities (P0-P3) and flag ambiguities
- Break features into epics → stories → tasks with estimates
- Create the epic/story/task hierarchy in ohno via MCP tools and write
.claude/PROJECT.md - Identify first skill to run and hand off
Skill Assignment
| Feature Type | Primary Skill | Secondary Skills |
|---|---|---|
| REST/GraphQL APIs | api-design | testing-strategy |
| Database schemas | database-design | — |
| SDK/library | sdk-development | — |
| Auth/Security | api-design | — |
| Testing infrastructure | testing-strategy | — |
| AWS/Cloud provisioning | cloud-infrastructure | — |
| Serverless/Lambda | cloud-infrastructure | api-design |
| Container deployment | cloud-infrastructure | ci-cd |
References
| Reference | Description |
|---|---|
| prd-analysis.md | Deep dive on document analysis |
| task-breakdown.md | Detailed breakdown methodology |
| kanban-setup.md | Legacy pre-ohno kanban generation (reference only — plan state lives in ohno) |
| skill-routing.md | Skill assignment logic |
| project-md-template.md | PROJECT.md template and format |
| database-schema.md | ohno internal SQLite schema (reference only — manage via MCP tools/CLI, never write the DB directly) |
| features-json.md | Legacy pre-ohno features.json format (reference only) |
| anti-patterns.md | Analysis, breakdown, and output anti-patterns |
| design-integration.md | Design plugin detection, UI/UX workflows, design-first routing |
| kanban-template.html | HTML template for interactive kanban board |
What ships with it
12 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.
- eval-log.md 20 KB
- eval.json 20 KB
- references/anti-patterns.md 1.6 KB
- references/database-schema.md 4.3 KB
- references/design-integration.md 7.6 KB
- references/features-json.md 1.6 KB
- references/kanban-setup.md 16 KB
- references/kanban-template.html 31 KB
- references/prd-analysis.md 9.6 KB
- references/project-md-template.md 1.2 KB
- references/skill-routing.md 9.3 KB
- references/task-breakdown.md 15 KB
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 · 67 lines · 42 tokens per session scan A 0b521a71a975
planning is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 819 once invoked, about $0.0002 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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…