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 sflandergan/agentic-coding --skill planning-structuregit clone --depth 1 https://github.com/sflandergan/agentic-codingWrote 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/sflandergan/agentic-coding/planning-structure)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/planning-structure"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/planning-structure/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/sflandergan/agentic-coding/planning-structure"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/planning-structure.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.00034 | $0.00721 |
| Opus 5.5 | $0.00014 | $0.00288 |
| Sonnet 5.5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
planning-structure 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Structure
This skill defines the artifact layout for multi-task implementation and review-fix plans. It does not own workflow behavior, quality rules, or role orchestration.
Implementation Plan Layout
plans/<feature-dir>/
spec.md
plan.md
tasks/
01-<task-slug>.md
02-<task-slug>.md
plan.md (summary index)
plan.md is the implementation entry point. It includes:
- Standard plan header (Goal, Architecture, Tech Stack)
- Docs used
- Verification baseline
- Ordered task overview table with columns: task number/title, objective, primary files touched, task-local verification, and a link to
tasks/NN-<slug>.md
Each task summary in the index must link to its task file using a relative path: [tasks/01-<slug>.md](tasks/01-<slug>.md).
tasks/*.md (executable task files)
Each implementation task file contains the full executable task:
- Task number and title
- Objective (one sentence)
- Exact files to create/modify/test with paths
- Dependencies on prior tasks if any
- Bite-sized checkbox steps with code, commands, and expected outcomes
- TDD details for behavior changes (failing test, verify fail, implement, verify pass, commit)
- Exact commands with expected outcomes
- Intended commit message
Task files must be self-contained. An implementer reading only the task file must be able to execute the task without reading the surrounding plan, spec, or other task files unless the task explicitly requires additional context.
Numbering and slug rules
- Task files use two-digit zero-padded numbers:
01-,02-, ...,99-. - Slugs are short kebab-case identifiers derived from the task title:
create-planning-structure-skill,update-workflow-planning. - The number prefix and slug are separated by a hyphen:
01-create-planning-structure-skill.md.
Review-Fix Plan Layout
Review fixes are organized into immutable, numbered rounds under review-rounds/.
Each round is a self-contained review-fix plan that can be implemented without reading earlier rounds.
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 · 88 lines · 34 tokens per session scan A 1cdc5e0e8ba4
planning-structure is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 721 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-09-13.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…