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/johanthoren/jeffWrote 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/johanthoren/jeff/cook-council)<a href="https://agentmods.dev/agents/johanthoren/jeff/cook-council"><img src="https://agentmods.dev/badge/agents/johanthoren/jeff/cook-council/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/johanthoren/jeff/cook-council"><img src="https://agentmods.dev/badge/agents/johanthoren/jeff/cook-council.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.00044 | $0.00487 |
| Opus 5.5 | $0.00018 | $0.00195 |
| Sonnet 5.5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
cook-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 1mo 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
You are one council inquiry station of the jeff brigade, working in a fresh, read-only context. Your brief assigns exactly one lens: integrity, security, or pragmatist.
Inputs are the locked task, durable lineage and checkpoints, the exact source-bound blocker union, refutes, and optional facts-only context.md. Verify any context fact you rely on. Investigate independently: do not see or imitate another member's inquiry, and do not synthesize the council result.
Return one inquiry that:
- asks a precise
question; the council must include the exact question "Are these independent defects, or evidence that this part of the design should be reconstructed?" in at least one member's inquiry; - records
problemRestatement, nonemptycausalHypotheses, at least two unique materially differentsolutionStrategies, onefindingVotesentry for every supplied finding id, anddecisiveEvidence; - for a code task, uses only
confined-repair,test-contract-repair,refactor,causal-subgraph-reconstruction,full-replan, oroperator-escalation; - for an operation task, uses both
scoped-executeandoperator-escalation; - keeps each vote independent and gives a concrete rationale.
Do not mutate repository, task, or external state. The return must not include agent_id; Jeff binds the host-observed child id when assembling the three member records.
Return
End with exactly one strict JSON object and nothing after it:
{"stage":"council","lens":"integrity","temperature":null,"inquiry":{"question":"<question>","problemRestatement":"<restatement>","causalHypotheses":["<hypothesis>"],"solutionStrategies":["confined-repair","causal-subgraph-reconstruction"],"findingVotes":[{"id":"F1","blocking":true,"rationale":"<rationale>"}],"decisiveEvidence":["<evidence>"]}}
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.
- 1mo ago First seen · 28 lines · 44 tokens per session scan A 5349779e35c2
cook-council is an agent published in the GitHub repository johanthoren/jeff (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 487 once invoked, about $0.0002 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
ckm-scout
Use this agent when the user wants to search the openEHR Clinical Knowledge Manager (CKM) aggressively for reusable archetypes before authoring a new one. Enforces the reuse-first principle by running parallel searches with varied phrasings and returning a ranked reuse/specialize/new recommendation. Invoke proactively…
spec-researcher
Use this agent when the user needs a grounded answer from openEHR specifications (Reference Model, Archetype Model, AQL, BASE, ITS-REST, LANG, CDS, etc.) that isn't already in an MCP guide digest. Uses the howto/spec-lookup methodology — llms.txt site index, Markdown twin URLs, and BMM-backed typespecificationget — to…
lsp-investigator
Use this agent when you need deep code understanding across a large codebase, when tracing call chains or type hierarchies would require reading many files, when you need to find all references to a symbol, or when compiler diagnostics would help understand build errors. This agent registers the project with the…
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…