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 Abilityai/abilities --skill plangit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/plan)<a href="https://agentmods.dev/skills/abilityai/abilities/plan"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/plan/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/abilityai/abilities/plan"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/plan.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.00032 | $0.02431 |
| Opus 5.5 | $0.00013 | $0.00972 |
| Sonnet 5.5 | $0.00006 | $0.00486 |
| Haiku 4.5 | $0.00003 | $0.00243 |
Grade A, and why
project-plan 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 1mo 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planner
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.project-plan vX.Y — recent: <summary>. Then proceed.
Purpose
Manage large projects that span multiple Claude sessions. On first run, analyze the project scope and produce a session-by-session execution plan. On subsequent runs, execute the next session and update state until the project is complete.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Project plan | project_plan.yaml |
Y | Y | Session plan, status, and history |
| Project inputs | User-provided files/description | Y | Raw project requirements | |
| Workspace files | Varies per project | Y | Y | Files modified during sessions |
Inputs
$0: Project name (used as prefix forproject_plan.yaml, e.g.,refactor→refactor_project_plan.yaml)$1: (Optional) Path to input file(s) with project requirements, OR verbal description
Process
Step 0: Detect Mode
Check if project_plan.yaml (or [name]_project_plan.yaml) exists and has incomplete sessions:
- No plan exists OR all sessions completed → Go to Phase A: Plan
- Plan exists with incomplete sessions → Go to Phase B: Execute
Parse any flags:
--status→ Show progress summary, then stop--plan <input>→ Force new plan creation (Phase A)--session N→ Jump to session N in Phase B--skip N→ Mark session N as skipped--abandon→ Mark project as abandoned--add "change"→ Append a change to the backlog
Phase A: Plan a New Project
A1: Gather Project Scope
Read all input materials:
- If input file(s) provided: read them fully
- If verbal description: capture from conversation
- Ask clarifying questions if scope is ambiguous
Identify:
- What changes: List every file, component, or system that needs modification
- What the changes are: For each item, what specifically needs to happen
- Dependencies: Which changes depend on others being done first
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.
- 1mo ago First seen · 329 lines · 32 tokens per session scan A d3dcfb4946e9
project-plan is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 2,431 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-30.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…