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 EvolveHQ/docflow --skill agent-wavegit clone --depth 1 https://github.com/EvolveHQ/docflowWrote 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/evolvehq/docflow/agent-wave)<a href="https://agentmods.dev/skills/evolvehq/docflow/agent-wave"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/agent-wave/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/evolvehq/docflow/agent-wave"><img src="https://agentmods.dev/badge/skills/evolvehq/docflow/agent-wave.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.00082 | $0.03472 |
| Opus 5.5 | $0.00033 | $0.01389 |
| Sonnet 5.5 | $0.00016 | $0.00694 |
| Haiku 4.5 | $0.00008 | $0.00347 |
Grade A, and why
agent-wave 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 11d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-wave
Run a declared batch of accepted queue items using the capabilities this host actually exposes. Budgets count items or waves. An optional hours cap stops new waves, never a running item. Long-lived automation uses the host's scheduling facility (see README); this session does not promise to outlive itself.
Preconditions and host capability
Before asking parameters, read the repository's entry point, conventions,
queue and autonomous prompt. Resolve all artefact paths, including _agent/,
against the recorded root. Require a real gate and the queue it walks.
| Recorded mode | Execution |
|---|---|
| Single writer | Stop and direct the operator to the sequential autonomous prompt, at every requested width. |
| Shared checkout, direct integration | One executor at a time in that checkout, using item status and lock rows. No claim branch or integration worktree. |
| Shared checkout, PR integration | Stop before claiming; require separate worktrees for PR waves. |
| Separate worktrees | Each executor uses its own worktree; integration follows the recorded model. |
Fetch/prune the recorded remote and require its integration branch. Print the fetched base SHA. Compare the local integration ref: report unpushed commits or divergence before proceeding, never silently discard them. A behind, clean checkout may be fast-forwarded when it is safe; otherwise leave it alone. The wave's state and probe come from the fetched base, not uncommitted files in the operator's checkout. If the remote queue is empty but the local queue differs, explain that difference.
Derive whether the host can delegate, isolate checkouts, run concurrently, use an orchestration facility already enabled by the operator, and require shaped results. Choose the highest available rung:
- Enabled orchestration facility: one fan-out for this wave only. Keep wave loops, clock checks and questions in the orchestrator.
- Plain subagents: parallel if available, sequential otherwise. Use host worktree isolation only if its starting head equals the declared base; otherwise explicitly create each worktree at that base.
- The orchestrator executes one item at a time, in its own worktree or the shared checkout as the recorded mode permits.
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.
- 11d ago Changed · +4 lines 4841628e4cd7
- 1mo ago Changed · +27 lines bb9c35286635
- 1mo ago Changed · +88 lines · -18 tokens per session 07446586174d
- 1mo ago Changed · -5 tokens per session d20f7e710d94
- 1mo ago Changed · +7 lines c4d1ec852f16
- 1mo ago First seen · 146 lines · 105 tokens per session scan A ec1fd84059ea
agent-wave is a skill published in the GitHub repository EvolveHQ/docflow (16 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 3,472 once invoked, about $0.0003 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
adr-integration
This skill should be used when the user asks about "ADR integration", "ADR CI/CD", "ADR tooling", "ADR automation", "export ADRs", "ADR documentation site", or needs guidance on integrating ADRs with CI/CD, documentation sites, and other tools.
adr-decision-drivers
This skill should be used when the user asks about "decision drivers", "architectural forces", "quality attributes", "how to identify trade-offs", "non-functional requirements for ADRs", or needs help identifying, documenting, and weighing the forces that influence architectural decisions.
adr-compliance
This skill should be used when the user asks about "ADR compliance", "architecture compliance", "ADR audit", "enforce ADRs", "check code against ADRs", "ADR violations", or needs guidance on auditing code compliance with accepted architectural decision records.
adr-fundamentals
This skill should be used when the user asks "what is an ADR", "when should I create an ADR", "ADR best practices", "architecture decision records", "ADR lifecycle", "how to document architecture decisions", or needs guidance on ADR fundamentals, when to create ADRs, or ADR lifecycle management.
adr-quality
This skill should be used when the user asks about "ADR quality", "review ADR", "ADR checklist", "improve ADR", "ADR validation", "good ADR examples", or needs guidance on evaluating, improving, and maintaining high-quality architectural decision records.
atlas-adr
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".