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/wsauret/flywheel/plannpx skills add wsauret/flywheel --skill plangit clone --depth 1 https://github.com/wsauret/flywheelWrote 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/wsauret/flywheel/plan)<a href="https://agentmods.dev/skills/wsauret/flywheel/plan"><img src="https://agentmods.dev/badge/skills/wsauret/flywheel/plan.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.00047 | $0.00885 |
| Opus 5 | $0.00023 | $0.00443 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
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 3d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Planning Workflow
MANDATORY FIRST ACTION — You MUST use the Skill tool to invoke the correct skill below BEFORE doing anything else. Do NOT read files, search code, or respond to the user first.
Determine which skill to invoke first based on the input:
- If the input is a slug (lowercase kebab, e.g.
feat-user-auth) that matches an existing session under.flywheel/plugin/sessions/<slug>-*whosespec.jsonexists: invokeplan-review(skip creation) - Otherwise (feature description, or a path to a design document ending in
-design.md): invokeplan-creation
Invoke the first skill NOW using the Skill tool:
skill: plan-creation
OR if the input resolves to an existing session with spec.json:
skill: plan-review
#$ARGUMENTS
Note: The current year is 2026.
IMPORTANT: Planning Mode Only
DO NOT WRITE OR EDIT ANY CODE DURING PLANNING!
This workflow is for research and planning only. Implementation happens in /work.
After the First Skill Completes
This orchestrator runs three skills in sequence. After each skill completes, immediately invoke the next one using the Skill tool. Do NOT stop between phases — select "continue" options when presented and invoke the next skill.
Full sequence:
[Input] → plan-creation → plan-review → plan-consolidation → [Present]
After plan-creation, the session dir at .flywheel/plugin/sessions/<session-id>/ contains the spec.json and session.json that subsequent skills read. The active pointer .flywheel/plugin/active.json is the connecting glue — no explicit path-passing between phases.
- plan-creation → writes
spec.json,session.jsoninto the session dir; updatesactive.json - plan-review → reads the active session's spec.json, writes
review.findings.json - plan-consolidation → merges
review.findings.jsonintospec.json; backs up pre-consolidation spec tospec.json.pre-consolidation
If the input was a slug that resolved to an existing session (review mode), start at step 2.
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.
- 3d ago First seen · 102 lines · 47 tokens per session scan A 3555f25c7be8
plan is a skill published in the GitHub repository wsauret/flywheel (14 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 885 once invoked, about $0.0002 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
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
best-of-n
Generate a small set of independent candidate solutions in worktrees, judge them against one explicit rubric, and apply the winner only after PASS verification.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
handoff
Write a compact, decision-ready handoff so the next session (or the user) can continue without reconstructing the current one. Use when the session is ending, context is running low, the user asks for a handoff / "pass the baton" / "hand off", or a long-running operation needs a durable state checkpoint.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.