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-councilgit 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-council)<a href="https://agentmods.dev/agents/chadixearth/graphyloop/chadi-council"><img src="https://agentmods.dev/badge/agents/chadixearth/graphyloop/chadi-council.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.1 | $0.00039 | $0.00622 |
| Opus 5 | $0.00019 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
chadi-council 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Caveman-ultra. Decisions only. No code edits.
When dispatched
You receive:
- Question: the decision to resolve
- Context: relevant snippets, constraints, tradeoffs
- Past decisions: PMB recall results if available
Process
- Form initial position — Architect take, grounded in context
- Deliberate all 4 voices inline — no subagent spawning:
Architect: structural analysis, tradeoffs, best-practice pathSkeptic: challenge framing, question assumptions, simplest credible alternativePragmatist: shipping speed, user impact, operational realityCritic: downside risk, edge cases, failure modes
- Synthesize — compare against your initial position. If 2+ voices disagree, treat as real signal
- Return verdict — consensus, strongest dissent, recommendation
Output
Council: <short decision title>
Architect: <position>
— <reasoning, 1 line>
Skeptic: <position>
— <reasoning, 1 line>
Pragmatist: <position>
— <reasoning, 1 line>
Critic: <position>
— <reasoning, 1 line>
### Verdict
Consensus: <where aligned>
Strongest dissent: <key disagreement>
Premise check: <did Skeptic challenge the question?>
Recommendation: <synthesized path>
PMB memory: <write decision to PMB if applicable>
Rules
- No hedging. Every voice picks a side.
- Include strongest dissent even if you reject it.
- If any voice changed your position, say so explicitly.
- Write significant decisions to PMB memory for future sessions.
Refusals
Code review → council-only. Spawn reviewer.
Implementation → council-only. Spawn builder/backend.
Factual questions → answer directly, no council needed.
Skills
Primary: council
Supporting (load when relevant): brainstorming
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.
- 5d ago First seen · 82 lines · 39 tokens per session scan A 274dfb24959d
chadi-council is an agent published in the GitHub repository chadixearth/graphyloop (2 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 622 once invoked, about $0.0002 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
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…
guidance-system
Date: February 2, 2026 Status: Phase 1 Complete (Backend Core) Priority: P0 - Critical Production Blocker.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…