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/worknpx skills add wsauret/flywheel --skill workgit clone --depth 1 https://github.com/wsauret/flywheelWhat 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.00049 | $0.04351 |
| Opus 5 | $0.00024 | $0.02176 |
| Sonnet 5 | $0.00010 | $0.00870 |
| Haiku 4.5 | $0.00005 | $0.00435 |
Grade A, and why
work 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 2d 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.
6. **Manual verification** — if `phase.manual_verification` is non-empty (plan mode), **you (the orchestrating agent) perform these checks yourself.** Do not surface them to the user. Do not call `AskUserQuestion`. You h How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Implementation Skill
Execute the active session's plan or review findings via probe → dispatch → checkpoint. Namespace: plugin uses .flywheel/plugin/sessions/.
Input
No required arguments. Optional $ARGUMENTS:
- empty → use the active session from
.flywheel/plugin/active.json - slug (
^[a-z0-9-]+$) → prefix-scan.flywheel/plugin/sessions/<slug>-*; tiebreak by most-recent date
Mode is detected from session contents — never set explicitly.
Phase 0: Session Detection
Active pointer lives at .flywheel/plugin/active.json ({ "schema_version": 1, "session_id": "<id>" }); sessions live at .flywheel/plugin/sessions/<session-id>/.
Decision tree:
- No args, active.json missing → error:
"No active session. Run /plan or /work <slug>."Exit. - No args, active.json points to missing session dir → error:
"Session <id> not found. Clearing active pointer."rm -f .flywheel/plugin/active.json. Exit. - No args, active.json present →
SESSION_ID=$(jq -r .session_id .flywheel/plugin/active.json); use it. - Slug arg → prefix-scan:
find .flywheel/plugin/sessions -maxdepth 1 -type d -name "${SLUG}-*" | sort -r. ISO-date suffix sorts lexically = chronologically; first result wins. Updateactive.jsonatomically (.tmp→mv) to the winner.
Stale-tmp cleanup: if progress.json.tmp or session.json.tmp exist from an interrupted prior write, delete them. The authoritative file is the un-suffixed one; partial writes never persist past a crash because .tmp → mv is atomic on local POSIX.
Validate session.json.schema_version == 1. Mismatch → "Unsupported schema version <N>. Re-run the producing skill to regenerate."
Phase 1: Mode Detection & Load
progress.json is the file the rest of the pipeline reads to know what's happening. work-review reads it to see what files you touched. /yolo reads it to detect the fix-findings transition. Future /work invocations read it to resume. Without progress.json, the rest of the pipeline can't see your work — even if the code is correct, nothing downstream knows you ran. Treat writing it as the first thing you do, not the last.
What ships with it
1 file 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.
- 2d ago First seen · 346 lines · 49 tokens per session scan A c44534b4fcbd
work is a skill published in the GitHub repository wsauret/flywheel (14 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 4,351 once invoked, about $0.0002 per session on Opus 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
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.