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-plan)<a href="https://agentmods.dev/commands/chadixearth/graphyloop/chadi-plan"><img src="https://agentmods.dev/badge/commands/chadixearth/graphyloop/chadi-plan/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-plan"><img src="https://agentmods.dev/badge/commands/chadixearth/graphyloop/chadi-plan.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.00013 | $0.00086 |
| Opus 5.5 | $0.00005 | $0.00034 |
| Sonnet 5.5 | $0.00003 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
chadi-plan 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. Do intake, acceptance criteria, discovery, architecture map, risk classification, and PARALLEL_PLAN.md (lanes, disjoint file ownership, contract and context-pack steps). Use matching skills and available LSP/ast-grep/context7 tools when relevant. Do not implement yet unless the user already asked to proceed.
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 · 13 tokens per session scan A eedd3bf06ffd
chadi-plan is a command published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 86 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.