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 peteromallet/Arnold --skill planninggit clone --depth 1 https://github.com/peteromallet/ArnoldWrote 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/peteromallet/arnold/planning)<a href="https://agentmods.dev/skills/peteromallet/arnold/planning"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/planning/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/peteromallet/arnold/planning"><img src="https://agentmods.dev/badge/skills/peteromallet/arnold/planning.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.00000 | $0.00580 |
| Opus 5.5 | $0.00000 | $0.00232 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authority status (M11): Zero-authority history. All repair, audit, and deployment authority has been migrated to canonical delegation. This document is retained for reference only — it must not be used to materialize commands, grant authority, or drive automated actions.
Planning Pipeline — Skill Reference
Overview
The megaplan pipeline (packaged at megaplan/pipelines/planning/) is the built-in megaplan plan-production substrate.
Its canonical registry identity is megaplan with the legacy alias planning → megaplan.
It orchestrates the full prepare → plan → critique/gate/revise loop →
finalize → execute → review lifecycle.
Gate verdict vocabulary
The gate stage emits a PipelineVerdict whose recommendation field is one
of the following GateRecommendation literals:
| Verdict | Meaning |
|---|---|
proceed |
Gate approved the plan; advance to finalize (and optionally execute). |
iterate |
Gate rejected the plan; re-enter the critique → revise loop. |
tiebreaker |
Evaluators are split; hand off to the tiebreaker stage for adjudication. |
escalate |
Quality ceiling reached at current tier; escalate to a higher-complexity model. |
Robustness levels
Robustness controls the depth of the critique/gate loop and the number of
evaluators engaged. Canonical names (accepted by --robustness / config):
| Level | Alias(es) | Behaviour |
|---|---|---|
bare |
tiny |
Single-pass, no gate loop. Fastest; for quick drafts. |
light |
— | One critique + revise round, minimal gate criteria. |
full |
standard |
Standard gate loop (default). Balanced quality/cost. |
thorough |
robust |
Extended gate loop, stricter criteria, more evaluators. |
extreme |
superrobust |
Maximum depth, all evaluators enabled. |
The default robustness when no --robustness flag is supplied is full.
Stage topology
prep → plan → critique ──→ gate ──proceed──→ finalize [→ execute → review]
↑ │
└──iterate────┘
│
└──tiebreaker──→ [adjudication] → finalize
What ships with it
4 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.
- 1mo ago First seen · 60 lines · 0 tokens per session scan A 9103b5ad3d31
planning is a skill published in the GitHub repository peteromallet/Arnold (98 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 580 tokens. 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-04.
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.
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,"…
remove
Remove a deployed framework or addon from the current workspace.