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 britt/agent-skills --skill project-planninggit clone --depth 1 https://github.com/britt/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/britt/agent-skills/project-planning)<a href="https://agentmods.dev/skills/britt/agent-skills/project-planning"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/project-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.00067 | $0.01127 |
| Opus 5 | $0.00034 | $0.00563 |
| Sonnet 5 | $0.00013 | $0.00225 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
project-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 6d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planning Skill
Orchestrate a comprehensive project planning workflow that generates GitHub issues, architecture diagrams, dependency graphs, and timeline charts from a natural language project description.
Prerequisites: Requires the issue-decomposition, architecture-diagramming, dependency-mapping, and timeline-planning skills (installed individually or via the project-foundations bundle). If a sub-skill is unavailable, perform that step inline.
When to Use
Activate this skill when user says:
- "Let's build a project plan for..."
- "Help me plan [project name]"
- "Create a project plan"
- "Break down this project"
- "Help me scope out..."
- "Plan the implementation of..."
Sub-Skills
This skill coordinates four specialized sub-skills:
| Skill | Purpose |
|---|---|
| issue-decomposition | Break down into GitHub issues |
| architecture-diagramming | Generate architecture diagrams |
| dependency-mapping | Map issue dependencies |
| timeline-planning | Create Gantt charts |
Planning Workflow
Step 1: Understand the Project
Ask key questions to scope the work:
-
Project Overview
- What is this project/feature?
- Who are the primary users?
- What problem does it solve?
-
Technical Context
- What technologies will be used?
- Are there existing patterns to follow?
- What external integrations are needed?
-
Constraints
- Any technical requirements or limitations?
- Dependencies on other work?
Step 2: Analyze Existing Codebase
If working in an existing project:
- Analyze the project structure
- Review existing code patterns
- Explore the project organization
Step 3: Decompose into Issues
Use the issue-decomposition skill to generate 5-15 well-structured issues with:
- User stories
- Acceptance criteria
- Dependencies
- Estimates
- Labels
Step 4: Generate Architecture Diagram
Use the architecture-diagramming skill to create a Mermaid diagram showing:
- Major components
- Data flow
- External integrations
- Boundaries and layers
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.
- 6d ago First seen · 188 lines · 67 tokens per session scan A 68b1accf4f21
project-planning is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 1,127 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.