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 RobLovesTech/AgenticFlyWheel --skill validate-checklistgit clone --depth 1 https://github.com/RobLovesTech/AgenticFlyWheelWrote 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/roblovestech/agenticflywheel/validate-checklist)<a href="https://agentmods.dev/skills/roblovestech/agenticflywheel/validate-checklist"><img src="https://agentmods.dev/badge/skills/roblovestech/agenticflywheel/validate-checklist/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/roblovestech/agenticflywheel/validate-checklist"><img src="https://agentmods.dev/badge/skills/roblovestech/agenticflywheel/validate-checklist.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.00036 | $0.00359 |
| Opus 5.5 | $0.00014 | $0.00144 |
| Sonnet 5.5 | $0.00007 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
validate-checklist 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 2mo 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.
What it actually says
Validate the target AFW CHECKLIST.yaml.
Process:
- Resolve
$ARGUMENTSto either:- a direct checklist path, or
docs/Agent Implementation Packets/<feature-slug>/CHECKLIST.yaml
- Read
AGENTS.mdfirst. - Prefer these sources:
prompts/CHECKLIST_VALIDATOR.mdorAgenticFlywheel/prompts/CHECKLIST_VALIDATOR.mdtemplates/aip/CHECKLIST.schema.json,docs/templates/AIP/CHECKLIST.schema.json, orAgenticFlywheel/templates/aip/CHECKLIST.schema.json- the target
CHECKLIST.yaml
- Check:
- required top-level fields
packet_level,requirements_mode,delivery_surfaces,enabled_modules, andomitted_moduleswhen present, plus legacy fallback behavior when they are absent- collaboration readiness task and Collaboration Summary write-back
- final
Docs & Handoffphase - verification commands and acceptance
- implementation audit, remediation, re-verification, and packet closure tasks
- status coherence
- registry update coverage
- top-level
in_progressorcompletedpackets do not omit completed collaboration readiness unless explicitly legacy with rationale
- Return pass or fail with findings and a minimal proposed patch.
If the target file cannot be found, explain the missing path and stop.
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.
- 2mo ago First seen · 32 lines · 36 tokens per session scan A 21e5d565f17a
validate-checklist is a skill published in the GitHub repository RobLovesTech/AgenticFlyWheel (2 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 359 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…