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 agent-rig/rig --skill rig-plangit clone --depth 1 https://github.com/agent-rig/rigWrote 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/agent-rig/rig/rig-plan)<a href="https://agentmods.dev/skills/agent-rig/rig/rig-plan"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-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/agent-rig/rig/rig-plan"><img src="https://agentmods.dev/badge/skills/agent-rig/rig/rig-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.00145 | $0.01602 |
| Opus 5.5 | $0.00058 | $0.00641 |
| Sonnet 5.5 | $0.00029 | $0.00320 |
| Haiku 4.5 | $0.00015 | $0.00160 |
Grade A, and why
rig-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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec → backlog planner
Turn a written spec into a reviewed plan and then a materialized backlog.
This is the front door for spec-driven work: you iterate on the spec, rig-plan
proposes the ticket structure, you approve it, and it creates the tickets. It
does not write code or cut branches — execution is /rig-epic and
/rig-task.
Unlike a fixed "epic breakdown," rig-plan is shape-agnostic: it decides, per chunk of the spec, whether the work is an epic, a sprint, or a single ticket.
Configuration
Reads .rig/config.json (defaults in parentheses):
tracker.provider—linear|github|none(none). Where tickets are created.none→ the plan is produced and written to a local file only.tracker.shapeLabels— GitHub-only labels applied at creation (epic/sprint) so a board / dispatcher can tell shapes apart.tracker.board— GitHub Projects v2 identity; when set, created tickets are added to the board via therig-trackeradapter.sourceScope[0]— the codebase area to sanity-check feasibility against.agents.architect(defaultrig-architect) — drives the decomposition.style.guideFile(.claude/STYLE.md) — how the plan and every ticket body it materializes are written.
Delegates ticket creation to /rig-epic (epic chunks), /rig-sprint (sprint
chunks), and /rig-issue (singletons). Hands execution to /rig-epic start /
/rig-task.
Arguments
[spec-file]— path to the spec (default: first ofSPEC.md,specs/prd.md,docs/prd.mdthat exists).--section <name>— plan only one section/milestone (match a heading). Good for "just plan Milestone 0 for now."--yes— skip the approval gate and materialize directly. Use only when the plan is trusted; the default is to STOP for review.
Procedure
-
Resolve config + the spec file. If none is found, ask for the path. Read the whole spec (or just the
--section). -
Decompose — fresh context,
agents.architect. Read the spec againstsourceScope[0]to ground feasibility, then produce a flat list of units and assign each a shape using the interleave test:- epic — several pieces that interleave: one piece's runtime contract
depends on another's incomplete state, or shipping one alone half-migrates
the system. These want a shared integration branch (
/rig-epic). - sprint — several pieces that are independent: each lands on the trunk on
its own (
/rig-sprint). - ticket — a single self-contained unit (
/rig-task//rig-issue).
- epic — several pieces that interleave: one piece's runtime contract
depends on another's incomplete state, or shipping one alone half-migrates
the system. These want a shared integration branch (
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 Changed · +2 lines feb6b95ec22a
- 1mo ago First seen · 107 lines · 145 tokens per session scan A a08232436adc
rig-plan is a skill published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session and 1,602 once invoked, about $0.0006 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
documentation
Use when the user asks to install or maintain a documentation index, keep CLAUDE.md or AGENTS.md inventories synchronized with files, add document metadata, classify documentation, or apply documentation-only setup to a repository.
infrastructure-project
Skill for the project management infrastructure module providing multi-project discovery, structure validation, and metadata extraction. Use when discovering active projects, validating project directory structure, or extracting project configuration metadata.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
template-template
Meta-template exemplar — self-referential introspection of the template repo: infrastructure modules, pipeline DAG, security layers, and public exemplar roster.
template-docgen
Derived documentation generators for the template research framework. Scripts that write to docs/generated/ and update in-place doc blocks.
spec-migration
Decide whether a change to the spec format needs a migration, and write it so agnostic-ai migrate rewrites old specs safely. Use when a change renames, replaces, deprecates, removes, or tightens any field users write under .agnostic-ai/ or in agnostic-ai.yaml.