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 lsantosweb/codex-agents-skills-kit --skill project-plannergit clone --depth 1 https://github.com/lsantosweb/codex-agents-skills-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/lsantosweb/codex-agents-skills-kit/project-planner)<a href="https://agentmods.dev/skills/lsantosweb/codex-agents-skills-kit/project-planner"><img src="https://agentmods.dev/badge/skills/lsantosweb/codex-agents-skills-kit/project-planner/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/lsantosweb/codex-agents-skills-kit/project-planner"><img src="https://agentmods.dev/badge/skills/lsantosweb/codex-agents-skills-kit/project-planner.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.00028 | $0.00423 |
| Opus 5.5 | $0.00011 | $0.00169 |
| Sonnet 5.5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
project-planner 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.
What it actually says
When to use
Use this skill when the task is:
- a new feature or new project
- a major refactor
- a multi-step implementation
- unclear and needs decomposition before coding
- dependent on choosing the right specialists in the right order
Core operating rules
- Planning mode does not write production code.
- Create a plan before implementation when the scope is broad or risky.
- Choose the project type explicitly: web, mobile, or backend.
- Route work to the narrowest relevant specialist.
- Define tasks with clear dependencies and verification criteria.
- Prefer small, reviewable milestones.
Planning workflow
- Read the request and extract goals, constraints, and risks.
- Classify the project type.
- Propose a minimal folder structure that fits the stack.
- Break work into phases and tasks.
- Assign the best specialist for each task.
- Define verification for each task.
- Save the plan in a task-named markdown file in the project root when the user wants a formal plan.
Routing guidance
- Web UI:
frontend-specialist - Mobile app:
mobile-developer - API/backend:
backend-specialist - Schema/data:
database-architect - Security review:
security-auditor - E2E/automation:
qa-automation-engineer - Performance:
performance-optimizer - Docs:
documentation-writer
Output structure
When producing a formal plan, include:
- overview
- success criteria
- stack and rationale
- file structure
- task breakdown
- dependencies
- verification checklist
Guardrails
- do not skip from idea to implementation without planning when the scope is complex
- do not assign both
frontend-specialistandmobile-developerfor the same UI surface unless the repo actually has both web and mobile apps - mark assumptions explicitly
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 · 61 lines · 28 tokens per session scan A 2566b5dd8dd3
project-planner is a skill published in the GitHub repository lsantosweb/codex-agents-skills-kit (2 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 423 once invoked, about $0.0001 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.
project-planner compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| project-plannerlsantosweb/codex-agents-skills-kit | Skill | 2 | 7mo ago | MIT | A | 28 | Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |