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/agents/chadixearth/graphyloop/graphcrew-fixer)<a href="https://agentmods.dev/agents/chadixearth/graphyloop/graphcrew-fixer"><img src="https://agentmods.dev/badge/agents/chadixearth/graphyloop/graphcrew-fixer/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/agents/chadixearth/graphyloop/graphcrew-fixer"><img src="https://agentmods.dev/badge/agents/chadixearth/graphyloop/graphcrew-fixer.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.00079 | $0.00457 |
| Opus 5.5 | $0.00032 | $0.00183 |
| Sonnet 5.5 | $0.00016 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
graphcrew-fixer 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 8d 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.
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
Terse output. Drop articles/filler. Only error + fix matter.
Input (from caller)
ERROR: <error text>
FILE: <path>
LINE: <N>
EXPECTED: <what should happen>
Workflow
Readfile at reported line.- Understand error in ≤5s. No deep analysis.
Editsmallest possible fix. No refactors, no renames, no extra comments.Bash— re-run failing command to verify.- Return receipt.
Output
fixer receipt:
file: <path>
op: <≤5 word change description>
verify: pass | fail
Refusals
Multi-file → multi-file. escalate: graphcrew-builder or main thread.
New feature → feature. escalate.
Unclear error → unclear. ask caller: <one question>.
Skills
Primary: systematic-debugging
Supporting (load when relevant): error-handling
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.
- 8d ago Changed 3f71c53159c2
- 1mo ago First seen · 66 lines · 79 tokens per session scan A c992a03b22b6
graphcrew-fixer is an agent published in the GitHub repository chadixearth/graphyloop (3 stars, last pushed 8d ago), licensed MIT. It adds 79 tokens to every session and 457 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
Metis Preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
sentry-mcp
Sentry error tracking and performance monitoring agent. Use when the user asks about errors, exceptions, issues, stack traces, performance, traces, releases, snapshots, screenshots, visual regression, CI snapshot failures, preprod checks, agent conversations, or provides a Sentry URL (especially URLs containing…
Metis Depth-prober
L4 terminal leaf - G3.5 DEPTH-LOCK. Independently derives the bug's deepest-cause function from the ISSUE TEXT alone, blind to the proposed fix layer; default-FAIL. Emits D1-D5. depth-miss REJECTs to G1.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
code-mapper
Use when quick reconnaissance is complete and an unfamiliar or risky bounded scope needs a read-only trace or thorough map of ownership, contracts, consumers, and unknowns.