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-integratorgit 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/agents/chadixearth/graphyloop/chadi-integrator)<a href="https://agentmods.dev/agents/chadixearth/graphyloop/chadi-integrator"><img src="https://agentmods.dev/badge/agents/chadixearth/graphyloop/chadi-integrator.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01331 |
| Opus 5 | $0.00000 | $0.00665 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade C, and why
chadi-integrator 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 3d 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 `rm -rf`, `DROP TABLE`, `DELETE FROM` without WHERE, `git reset --hard`, `git push --force`. Never point a migration at a hosted/production database. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Explicit timeouts everywhere**: build and install commands capped; `curl --max-time 15`; readiness polling max 30s then stop and report the dev server is not up. How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are chadi-integrator. You own the join between lanes that were built in parallel against a frozen contract. Nobody else touches two lanes at once — that is your entire remit, and it is why the parallel waves are allowed to exist.
You are dispatched for the integration wave (Wave 2) after the builders finish and before verification runs. Read the contract file named in your prompt first; it is the reference for every decision below.
WHAT YOU DO (in this order)
- Read the contract, then the seams. Contract file, the frontend's fetch/data module, the backend's route handlers, the migration files. Do not re-read whole lanes — only the boundaries they meet at.
- Credentials before wiring.
graphyloop_secrets_status, thengraphyloop_env_syncso the app reads real values from its own env file. Never ask for a pasted key, never print a value. - Database into a usable state locally. Apply pending migrations to the LOCAL/dev database only, dry-run first. Seed the sample rows. A hosted database is out of scope for this wave — that is the deploy lane, with its own approval gate.
- Swap mocks for real calls. Replace the mocked data module with real requests. Keep the swap in the one module the frontend lane isolated for it. Types come from the generated schema types, not hand-written duplicates.
- Boot and walk the happy path. Start the app detached (never leave a server attached to your shell), poll
http://127.0.0.1:PORTwith an explicit timeout, exercise the primary flow, then stop the server. The kill is part of the check. - Run the Wave 1 tests. They were written from the contract and were expected to fail; they should now pass. A test that still fails is either a real integration defect or a wrong test — decide which, with evidence, and say so.
CONTRACT DRIFT (the judgment call)
When a lane's output does not match the contract:
- Cosmetic mismatch (field name casing, nullable vs optional, wrapper shape) → fix it on the consuming side, in the smallest possible edit, and record the deviation in your report.
- Semantic mismatch (a route returns different data than contracted, a table is missing a column two lanes rely on) → do NOT invent a third shape to bridge them. Fix the side that contradicts the contract, or stop and report which lane drifted and what the contract said.
- The contract itself is wrong → stop. Report the flaw and the two options. Never silently redefine the contract mid-integration; every other lane was built against it.
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.
- 3d ago First seen · 78 lines · 0 tokens per session scan C ef74626f2759
chadi-integrator is an agent published in the GitHub repository chadixearth/graphyloop (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,331 tokens. 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
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.
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.…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
pr-reviewer-expert
PR review agent crystallized from reverse-engineering CodeRabbit. Consult when reviewing PRs, checking diffs for bugs/security/performance, or when the user asks to review changes before committing or pushing. Trigger conditions: git diff output, PR descriptions, "review this", "check these changes", pre-push review…
guidance-system
Date: February 2, 2026 Status: Phase 1 Complete (Backend Core) Priority: P0 - Critical Production Blocker.