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 wsauret/flywheel --skill plan-creationgit 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-creation)<a href="https://agentmods.dev/skills/wsauret/flywheel/plan-creation"><img src="https://agentmods.dev/badge/skills/wsauret/flywheel/plan-creation/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/wsauret/flywheel/plan-creation"><img src="https://agentmods.dev/badge/skills/wsauret/flywheel/plan-creation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Output Handling · line 195 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00102 | $0.03719 |
| Opus 5.5 | $0.00041 | $0.01488 |
| Sonnet 5.5 | $0.00020 | $0.00744 |
| Haiku 4.5 | $0.00010 | $0.00372 |
Grade A, and why
plan-creation scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"manual_verification": "Optional: curl http://localhost:3000/healthz to verify the route responds." How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Creation Skill
Research the codebase, validate technical claims, and emit a work-ready spec.json in a single pass. Output validates against flywheel/schemas/task-list.schema.json.
Core Principles
- Codebase reality first — dispatch locators before hypothesizing patterns.
- Decisions, not code — capture approach, boundaries, risks, test scenarios. Do not pre-write implementation code.
- Executable-from-day-one — if you can't commit to concrete file paths or test scenarios, surface an
open_questioninstead of a vague task. - BLOCKING: Validate high-risk claims — security, payments, crypto, migrations, privacy trigger external validation via Context7.
Input
Feature description via $ARGUMENTS. If empty, ask user.
Phase 0: Check for Existing Knowledge
Before codebase research, check existing knowledge (skip missing dirs):
- Standards (
docs/standards/) — Search by tags for reusable patterns. - Solutions (
docs/solutions/) — Verified fixes from past work (up to 5 matches). - Research (
docs/research/) — Recent research within 30 days:find docs/research -name "*<topic-keywords>*" -mtime -30 2>/dev/null | head -3
If relevant knowledge found, use it as starting point for Phase 1. Fold key references into context.constraints[] or context.patterns[] so they survive into the dispatch.
Phase 1: Understand Codebase Context
BLOCKING: Do NOT use Read/Grep/Glob for TARGET CODEBASE research — dispatch locator Tasks first, then feed results to analyzer Tasks. Skill references, plan artifacts, and template files are exempt.
Run the canonical research workflow: all four locators in parallel → consolidate → all four analyzers in parallel. Read flywheel/skills/flywheel-conventions/references/research-workflow.md for locator templates, the consolidation rule, and analyzer templates.
After the canonical workflow completes, also check CLAUDE.md for team conventions (if analyzer-docs didn't already surface it) and recent similar features for precedent.
What ships with it
2 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 · 298 lines · 102 tokens per session scan A 022cf2748ece
plan-creation is a skill published in the GitHub repository wsauret/flywheel (14 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 3,719 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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 fleet 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.
plugin-creator
Scaffold a local Codewhale plugin bundle with a versioned manifest, namespaced Skills, and an explicit trust review.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.