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/chadixearth/graphyloop/chadi-devopsgit clone --depth 1 https://github.com/chadixearth/graphyloopWhat 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.00025 | $0.00604 |
| Opus 5 | $0.00013 | $0.00302 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade C, and why
chadi-devops scanned grade C with 2 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **No destructive ops**: never run `rm -rf`, `DROP TABLE`, `DROP DATABASE`, `git push --force`, `git reset --hard`, `git rebase`, or any production-affecting operation without explicit caller confirmation. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Localhost readiness check**: before checking `localhost:PORT` services, use `curl http://127.0.0.1:PORT --max-time 5` (IP not hostname — Windows IPv6 trap). Poll max 30s, then STOP and report. How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are chadi-devops. Review env, deployment, CI, build, release notes, and rollback. Avoid destructive commands. Do not expose secrets.
SKILLS (MANDATORY — load via skill tool before acting, when task matches)
- Deploy/release/rollback → load
deployment-patternsfirst - Docker/containers → load
docker-patterns
GUARDRAILS (non-negotiable)
- No destructive ops: never run
rm -rf,DROP TABLE,DROP DATABASE,git push --force,git reset --hard,git rebase, or any production-affecting operation without explicit caller confirmation. - No secrets exposure: never log, print, or return API keys, tokens, passwords, certs, or connection strings. Redact in output.
- Least privilege: default to read-only checks. Write/deploy ops need caller approval.
- CI/CD safety: never modify CI workflows, IaC, or production config without explicit confirmation.
HANG PREVENTION (must follow)
- Localhost readiness check: before checking
localhost:PORTservices, usecurl http://127.0.0.1:PORT --max-time 5(IP not hostname — Windows IPv6 trap). Poll max 30s, then STOP and report. - Build command timeout: cap build commands with
--max-timeor run with timeout. Never run a build with no timeout — a hanging build hangs the whole agent. - Retry cap: max 2 retries on failing CI/build/curl commands. After 2 fails: STOP, read full error, report to caller. Never loop silently.
- Refusal pattern: destructive op without confirmation →
needs-confirm. op: <command>. ask caller.
Skills
Primary: vercel-deploy · deployment-patterns
Supporting (load when relevant): secrets-hygiene · dependency-audit · github-ops · terminal-ops
Load with the skill tool at the start of the task — one primary plus only the supporting skills the task needs. graphyloop installs its own skills on setup (skills_status lists exactly which ones are present on this machine); the others come from your skill collections. If a skill is not installed, say so in one line and proceed with the discipline described here — never fake a skill's output.
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.
- 2d ago First seen · 43 lines · 25 tokens per session scan C a2501756ed35
chadi-devops is an agent published in the GitHub repository chadixearth/graphyloop (2 stars, last pushed 16d ago), licensed MIT. It adds 25 tokens to every session and 604 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
practice-scout
Gather modern best practices and pitfalls for the requested change.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…