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 rileyhilliard/claude-essentials --skill planning-productsgit clone --depth 1 https://github.com/rileyhilliard/claude-essentialsWrote 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/rileyhilliard/claude-essentials/planning-products)<a href="https://agentmods.dev/skills/rileyhilliard/claude-essentials/planning-products"><img src="https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/planning-products/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/rileyhilliard/claude-essentials/planning-products"><img src="https://agentmods.dev/badge/skills/rileyhilliard/claude-essentials/planning-products.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01131 |
| Opus 5 | $0.00022 | $0.00566 |
| Sonnet 5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
planning-products 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Products
Core principle: Define the problem worth solving and the experience worth building before deciding how to build it. Research what exists, understand who needs it, scope what matters.
Planning Phase
Load the relevant reference based on where you are in the planning process:
| Phase | Load | File |
|---|---|---|
| Researching market, competitors, existing patterns | Discovery | references/discovery.md |
| Framing the problem, users, and jobs to be done | Definition | references/definition.md |
| Defining how the feature should feel (UX or DX) | Experience | references/experience.md |
| Drawing scope boundaries, MVP, phasing | Scoping | references/scoping.md |
| Writing the actual product spec document | Template | references/feature-spec-template.md |
Start with Discovery when beginning from scratch. Start with Definition when the problem is already understood. Load Experience alongside either when the feature has significant interaction design. Load Scoping when you need to cut.
The Planning Sequence
Discovery → Definition → Experience → Scoping → [Hand off]
↓ ↓ ↓ ↓
Research Problem How it What's in
& patterns & users feels & what's out
Not always linear. Discovery can reframe the problem. Experience constraints can force scope changes. Scoping can send you back to discovery. But this is the default order.
Product Type Adjustments
Different products need different emphasis. Adjust the planning weight:
| Product type | Heavy on | Light on | Key question |
|---|---|---|---|
| Consumer (B2C) | Experience, discovery | Formal definition | "Would I use this?" |
| B2B / Enterprise | Definition, scoping | Visual polish | "Does this solve a workflow?" |
| Developer tools | DX experience, API ergonomics | Marketing polish | "Is this the obvious API?" |
| Internal tools | Scoping, definition | Discovery | "Does this save time?" |
| Platform / API | Definition, experience (DX) | Consumer UX | "Is this composable?" |
What ships with it
5 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.
- 10d ago First seen · 113 lines · 44 tokens per session scan A b4a704ecc579
planning-products is a skill published in the GitHub repository rileyhilliard/claude-essentials (128 stars, last pushed 22d ago), licensed MIT. It adds 44 tokens to every session and 1,131 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-30.
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…