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/razaib-khan/forgeweave/plannernpx skills add Razaib-khan/ForgeWeave --skill plannergit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/razaib-khan/forgeweave/planner)<a href="https://agentmods.dev/skills/razaib-khan/forgeweave/planner"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/planner.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.1 | $0.00021 | $0.00647 |
| Opus 5 | $0.00010 | $0.00324 |
| Sonnet 5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
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 5d 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.
Planner
Purpose
Transform vague, high-level user intent into a concrete, actionable execution plan. Breaks down complex goals into ordered steps, identifies dependencies, assesses risks, and determines which tools or agents are needed at each stage.
When to Use
- The user says "I want to build X" or "implement Y" without specifying how
- Multiple steps are needed and the order matters
- Different parts of the task require different tools or skills
- The task has dependencies that must be resolved in sequence
When Not to Use
- The user has already given step-by-step instructions — execute directly
- The task is a single, well-defined action (e.g., "rename this function")
- The task is purely research — use
deep-researchorquick-research
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
goal |
string | Yes | What the user wants to accomplish |
context |
string | No | Project context, constraints, or existing work |
available_skills |
array | No | Which skills are available for execution |
Expected Outputs
A structured plan containing:
- Goal restatement (clarified)
- Ordered steps with dependencies
- Required tools or skills per step
- Risk assessment per step
- Estimated complexity
Exact Workflow Steps
- Clarify the goal by restating it and asking for confirmation if ambiguous
- Decompose into ordered, atomic steps
- Identify dependencies between steps (blocking, parallel, sequential)
- Map each step to required tools, skills, or agents
- Assess risks per step (e.g., "this step may break existing tests")
- Present the plan for user approval before execution
Required Checks
- Goal is clarified and unambiguous
- Steps are ordered with dependencies identified
- Each step maps to an available tool or skill
- Risks are documented
Failure Modes
| Failure Condition | Response |
|---|---|
| Goal is too vague to decompose | Ask clarifying questions iteratively |
| No available skill covers a step | Report as uncovered and suggest creating a new skill |
| Steps have circular dependencies | Restructure to break the cycle |
What ships with it
3 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.
- 5d ago First seen · 88 lines · 21 tokens per session scan A 8f5f53663555
Planner is a skill published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 647 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-31.
Other skills, from other repositories
hex-release
Guides interactive Hex package release for AgentJido repos. Supports automated (GitHub Actions workflowdispatch) and manual release flows. Uses gitops for version bumping and changelog generation. Triggers on: release, hex publish, bump version, new release, publish package.
pr-review
Review a Pull Request for code quality, tests, merge conflicts, and readiness to merge.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.