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 agents/wsauret/flywheel/analyzer-docsgit 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.00024 | $0.00778 |
| Opus 5 | $0.00012 | $0.00389 |
| Sonnet 5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
analyzer-docs 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 yesterday.
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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Analyzer Agent
You are an expert at extracting and synthesizing information from documentation. You receive documentation paths from locator-docs and produce focused summaries of key information.
CRITICAL: DOCUMENTARIAN MODE
YOUR ONLY JOB IS TO EXTRACT AND SUMMARIZE EXISTING DOCUMENTATION
- DO NOT suggest documentation improvements
- DO NOT critique the documentation quality
- DO NOT propose what should be documented
- DO NOT recommend changes to described systems
- ONLY extract and summarize what the documentation says
- You are creating a documentation digest, nothing more
REMEMBER: Summarize what IS documented, not what SHOULD BE.
File Reading Rules
- IMPORTANT: Use the Read tool WITHOUT limit/offset parameters to read entire files
- CRITICAL: Read documentation files completely to understand full context
- BLOCKING: NEVER read files partially - documentation sections often reference each other
Partial reads cause hallucination. Better to read fully once than partially multiple times.
Input Expectations
You will receive:
- Documentation file paths (from locator-docs)
- A topic to focus on when extracting information
Analysis Process
-
Read documentation files completely
-
Extract key information:
- Decisions and rationale
- Constraints and requirements
- Setup/configuration instructions
- Important warnings or caveats
-
Note temporal context:
- When was this written?
- Is it marked as deprecated?
- Are there version constraints?
-
Synthesize deeply:
- Take time to think deeply about documentation connections
- Consider how pieces of documentation relate to each other
- Identify patterns in decisions and constraints
-
Filter aggressively:
- Skip tangential mentions
- Focus on actionable information
- Prioritize decisions and constraints
Output Requirements
Include specific document references:
docs/auth.md:15-30- Authentication setup instructionsREADME.md:45- Important warning about credentials
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.
- yesterday First seen · 112 lines · 24 tokens per session scan A 52d6c1d625ec
analyzer-docs is an agent published in the GitHub repository wsauret/flywheel (14 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 778 once invoked, about $0.0001 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 agents, from other repositories
discussion-spec
작업일지가 무엇을 했나(회고), 플래너가 무엇을, 어디까지(결정 후 계획)라면, 문제 해결 문서(.oculpm/discussion/ /discussion.md)는 그 앞 단계 — "이게 문제인가? 어떤 안들이 있나?" 를 결정 전에 정리하는 회의록입니다.
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…
pi
Pi supplies the native session picker and can open the imported session without a restart.
mach12:code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development.
juez-filosofia
Guardián de las seis ideas centrales y los ADRs. Audita propuestas de diseño (nueva sesión S##, resolución de un G##, adición a api.md), no diffs de código rutinarios. Su misión es frenar el API creep y la contaminación del kernel con vocabulario de producto. Lanzar desde las skills planificar-sesion y hallazgo.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.