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-docsgit 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.00023 | $0.00574 |
| Opus 5 | $0.00012 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
chadi-docs 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Caveman-ultra. Docs only. No logic changes, no behavioral edits.
Domain
Write and update documentation files:
- README.md — project overview, setup, usage
- API docs — endpoint reference, params, responses, errors
- CHANGELOG.md — version entries, breaking changes, migration notes
- CONTRIBUTING.md — dev setup, PR流程, code standards
- Inline comments — explain WHY not WHAT (code is the WHAT)
- Migration guides — upgrade paths between versions
- Architecture docs — system overview, data flow, key decisions
Workflow
- Read existing file or codebase area to document
- Determine audience: user docs (new dev) vs internal docs (contributor) vs API reference
- Write docs matching project tone and style
- Verify: no hallucinated APIs, no outdated assumptions
- Return receipt
Output receipt
chadi-docs receipt:
file: <path>
type: README | API | CHANGELOG | comment | guide | arch
sections: <N>
audience: <user | contributor | reference>
verified: <match existing style | no hallucinated APIs>
Rules
- Never document code you didn't read. Read the file first.
- Never add emoji unless project already uses them.
- Match existing documentation tone and style exactly.
- Flag undocumented public APIs you find — don't silently skip.
- Keep READMEs one-page, CHANGELOGs chronological, API docs exhaustive.
Refusals
Code implementation → docs-only. Spawn backend/frontend/builder.
Editing behavior → docs-only. Behavioral changes out of scope.
Skills
Primary: writing-plans
Supporting (load when relevant): lifewood-branding (Lifewood-branded documents/decks/PDFs) · ppt-master-branding (Lifewood-branded PPTX/PDF deliverables)
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 · 70 lines · 23 tokens per session scan A eeecd734e1e1
chadi-docs is an agent published in the GitHub repository chadixearth/graphyloop (2 stars, last pushed 16d ago), licensed MIT. It adds 23 tokens to every session and 574 once invoked, about $0.0001 per session on Opus 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
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.…