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 chriscox/agent-skills --skill project-plannergit clone --depth 1 https://github.com/chriscox/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/chriscox/agent-skills/project-planner)<a href="https://agentmods.dev/skills/chriscox/agent-skills/project-planner"><img src="https://agentmods.dev/badge/skills/chriscox/agent-skills/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/chriscox/agent-skills/project-planner"><img src="https://agentmods.dev/badge/skills/chriscox/agent-skills/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.00131 | $0.01842 |
| Opus 5.5 | $0.00052 | $0.00737 |
| Sonnet 5.5 | $0.00026 | $0.00368 |
| Haiku 4.5 | $0.00013 | $0.00184 |
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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planner
Prerequisites
- git
- gh (GitHub CLI, authenticated via
gh auth login)
Triage user input into the right project artifact: a proposal (big idea with phases), a feature issue (small enhancement), or a bug report (something's broken).
Repo Discovery
Before doing anything, discover the current repo's configuration:
- Run
git rev-parse --show-toplevelto find the repo root - Check for
.project-planner.ymlat the repo root — if it exists, read it and use its values for all paths, labels, and conventions - If no config file, fall back to auto-discovery:
- Proposal template: look for
docs/proposals/TEMPLATE.md - Issue templates: look in
.github/ISSUE_TEMPLATE/ - Docs directory: look for
docs/,mkdocs.yml - If nothing found, use the fallback formats bundled with the skill
- Proposal template: look for
- If the repo has
CLAUDE.mdorCONTRIBUTING.md, read for conventions - Run
gh repo view --json name,ownerto confirm the repo for issue creation
Config File: .project-planner.yml
Optional config file at repo root. All fields are optional — auto-discovery fills gaps.
See project-planner.yml in the skill directory for a copy-paste starter.
project: MyProject # project name (for issue titles)
repo: owner/repo # GitHub repo (usually auto-detected)
proposals:
dir: docs/proposals # where proposal docs live
template: docs/proposals/TEMPLATE.md # proposal template to follow
index: docs/proposals/index.md # index file to update with new proposals
mkdocs_nav: true # update mkdocs.yml nav when creating proposals
issues:
labels:
feature: enhancement # label for feature issues
bug: bug # label for bug issues
# branch_prefix: feature/ # branch naming prefix
# conventions:
# docs: docs # where project docs live
Triage Rules
Determine the type by asking: does this need design work or multiple phases?
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.
- 2mo ago First seen · 177 lines · 131 tokens per session scan A 47de4861c7c7
project-planner is a skill published in the GitHub repository chriscox/agent-skills (11 stars, last pushed 7mo ago), licensed MIT. It adds 131 tokens to every session and 1,842 once invoked, about $0.0005 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.
Other skills, from other repositories
roblox-team
Use to coordinate multiple parallel agents working on independent slices of a Roblox project. Use when the user says "split this work", "dispatch parallel agents", "run these in parallel", "team up on this", "swarm this refactor", or when a roblox-plan identified independent steps that can run concurrently.
roblox-scrum-planning
Generate and update the sprint status tracking board from Roblox epics. Use when the user says "run sprint planning", "generate sprint plan", or "update scrum board".
roblox-scrum-retrospective
Closes a sprint, audits completed stories, evaluates key learnings, and marks epics as done. Use when the user says "run retrospective", "close sprint", or "end epic [num]".
roblox-scrum-correct-course
Adjusts sprint scopes, manages blockers, or changes project directions mid-sprint. Use when the user says "correct course", "change sprint scope", or "manage blocker".
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…