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 agentmods add skills/lucasduys/forge/planningnpx skills add LucasDuys/forge --skill planninggit clone --depth 1 https://github.com/LucasDuys/forgeWrote 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/lucasduys/forge/planning)<a href="https://agentmods.dev/skills/lucasduys/forge/planning"><img src="https://agentmods.dev/badge/skills/lucasduys/forge/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 | $0.00022 | $0.01663 |
| Opus 5 | $0.00011 | $0.00831 |
| Sonnet 5 | $0.00004 | $0.00333 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
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 4d 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.
Planning Skill
This skill guides the decomposition of approved specifications into executable task frontiers. Each frontier is a dependency-ordered list of tasks grouped into parallelizable tiers.
Inputs
You will receive:
- Spec files: One or more approved spec files from
.forge/specs/ - Depth:
quick,standard, orthorough - Repo config: From
.forge/config.json(may include multiple repos with ordering) - Capabilities: From
.forge/capabilities.json(optional, informs task design) - Knowledge graph:
graphify-out/graph.json(optional, enables architecture-aware decomposition) - Design system: DESIGN.md (optional, enables design-tagged UI tasks)
Procedure
Step 1: Read and Validate Specs
For each spec file in .forge/specs/ (or the filtered subset):
- Read the file and parse its YAML frontmatter
- Verify
status: approved— skip any spec that is not approved - Extract all R-numbered requirements and their acceptance criteria
- Note the
linked_reposfield — this determines which repos tasks will target - Note the
complexityfield — this informs task sizing
Step 2: Determine Depth Parameters
Reference references/token-profiles.md for depth-specific settings:
| Parameter | Quick | Standard | Thorough |
|---|---|---|---|
| Tasks per spec | 3-5 | 6-12 | 12-20 |
| Tokens per task | ~3k | ~6k | ~12k |
| Review steps | None | After critical tasks | After every task |
| TDD enforcement | No | If skill available | Always |
| Phase verification | Skip | Quick check | Full goal-backward |
Step 2.5: Load Architecture Context (optional)
Knowledge Graph: If graphify-out/graph.json exists, load it and extract:
- God nodes (highest-connectivity concepts) for task prioritization
- Community structure for aligning task boundaries with module boundaries
- Cross-module dependencies for implicit dependency edges in the DAG
See skills/graphify-integration/SKILL.md for details.
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.
- 4d ago First seen · 177 lines · 22 tokens per session scan A 4d5e7cac978c
planning is a skill published in the GitHub repository LucasDuys/forge (55 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,663 once invoked, about $0.0001 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-30.
Other skills, from other repositories
coding-agent-standards
Defines practical standards for implementation-focused coding agents. Use when creating or editing code, especially when reliability, clarity, and low-risk delivery are required.
prompt-architect
Designs clear, testable prompts for agent workflows. Use when creating new prompts, refining weak prompts, or establishing reusable prompting patterns.
verification-agent
Provides a structured verification workflow for code and prompt outputs. Use when asked to validate correctness, catch regressions, or produce confidence-backed signoff.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.