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-deploy)<a href="https://agentmods.dev/commands/chadixearth/graphyloop/chadi-deploy"><img src="https://agentmods.dev/badge/commands/chadixearth/graphyloop/chadi-deploy/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-deploy"><img src="https://agentmods.dev/badge/commands/chadixearth/graphyloop/chadi-deploy.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.00021 | $0.00191 |
| Opus 5.5 | $0.00008 | $0.00076 |
| Sonnet 5.5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
chadi-deploy 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. Deploy lane (tool names are bare; OpenCode prefixes graphyloop_, Claude Code mcp__graphyloop__). 1) preflight target=deploy — every blocker must be cleared first (missing VERCEL_TOKEN, no build script, env file not git-ignored). 2) Mirror every runtime env key in the Vercel project; a local .env.local is not deployed. 3) Apply pending database migrations before the app deploy, dry-run first, with a rollback note. 4) Run the local build, then a PREVIEW deployment and verify the real URL, waiting with the tool's blocking command (never a sleep loop). 5) Production deploy only after explicit user approval, and record the rollback command in the report. Never print a credential value.
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 · 21 tokens per session scan A c3110c335f91
chadi-deploy is a command published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 191 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
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
pull
Refreshes local project state from a linked Supabase project or branch in one step, instead of running config pull, db pull, migration fetch, and functions download individually. It runs four steps, always in this order: pull config into supabase/config.toml, optionally fetch the remote migration history table into…
boss:ship
A command that builds, deploys, and health-checks a project that has already passed testing, then records the release details in a deployment report.
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
wa-guardrails
Generate preventive Well-Architected guardrails — AWS Config rules, Service Control Policies, permission boundaries, CloudWatch alarms, and IaC policy checks (CDK Aspects, cfn-guard, OPA/Sentinel) — so a workload stays aligned with Well-Architected best practices over time instead of being assessed once.
cost-optimization-review
Run a pillar-scoped Well-Architected review focused on the Cost Optimization pillar.