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.
git clone --depth 1 https://github.com/chadixearth/graphyloopWrote 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/commands/chadixearth/graphyloop/chadi-waves)<a href="https://agentmods.dev/commands/chadixearth/graphyloop/chadi-waves"><img src="https://agentmods.dev/badge/commands/chadixearth/graphyloop/chadi-waves/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/commands/chadixearth/graphyloop/chadi-waves"><img src="https://agentmods.dev/badge/commands/chadixearth/graphyloop/chadi-waves.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.00025 | $0.00187 |
| Opus 5.5 | $0.00010 | $0.00075 |
| Sonnet 5.5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
chadi-waves 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 today.
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
Use agent-chadi. Call plan_feature with the user's request as the goal (tool names are bare; OpenCode prefixes graphyloop_, Claude Code mcp__graphyloop__). Report the wave table (which lanes run in parallel, what each owns, what gates the deploy). Wave 0 writes the context pack (ctx-.md) and the frozen contract (contract-.md) alone. Then pass plan.tasks to task_distribute and dispatch ONLY the tasks it returns in dispatchNow. After each result, task_record it and dispatch whatever that unblocked, all tasks of a wave in ONE parallel call. Every lane brief ends with the turn-economy footer. Do not let a builder start before the contract and ctx files exist. Never poll.
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.
- today First seen · 6 lines · 25 tokens per session scan A f22523851128
chadi-waves is a command published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 187 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-10-29.
Other commands, from other repositories
handoff
Produce a structured handoff note for the current session.
retro
End-of-session retrospective - what worked, what to codify.
todo-triage
Sort TODO.md into Now / Soon / Parking lot with success criteria.
council
Run a persona council review with parallel subagents.
review
Review recent changes through the Code Reviewer and QA lenses.
drift-check
Run the agent doc alignment check.