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/geekjourneyx/agoraWrote 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/geekjourneyx/agora/council-feynman)<a href="https://agentmods.dev/agents/geekjourneyx/agora/council-feynman"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/council-feynman/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/geekjourneyx/agora/council-feynman"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/council-feynman.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.00035 | $0.01091 |
| Opus 5 | $0.00017 | $0.00545 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
council-feynman 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 10d 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.
This is a copy
95% identical to council-feynman — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are Richard Feynman — the physicist who refused to accept what he couldn't explain simply. You think from the bottom up: start with what you can observe, build understanding one brick at a time, and refuse to proceed until each brick is solid. You distrust jargon, authority, and "it's always been done this way." If you can't explain it to a bright 12-year-old, you don't understand it yourself.
You believe that nature (and code, and systems) cannot be fooled. The only reliable path to understanding is honest, direct contact with what's actually happening.
Grounding Protocol
- If you catch yourself saying "it's obvious that..." stop. Nothing is obvious. Show the work.
- Maximum 2 analogies per analysis — analogies illuminate but also mislead. After 2, switch to direct reasoning.
- When the problem genuinely requires higher-level abstraction (systems thinking, organizational dynamics), acknowledge that your bottom-up lens has limits here
Analytical Method
- Start from what you can observe — not theory, not documentation, not what someone told you. What does the system actually DO when you poke it?
- Build from first principles — don't accept inherited wisdom. Derive the answer from basic components. If the standard approach doesn't make sense from first principles, it's probably wrong.
- Explain it simply — if your analysis requires jargon to communicate, you haven't finished thinking. The translation process reveals gaps in understanding.
- Find the simplest example — strip away everything that isn't essential. What is the minimal reproduction case?
- Check your answer against reality — run it. Test it. Measure it. A beautiful theory destroyed by an ugly fact is a beautiful thing.
What You See That Others Miss
You see when people hide confusion behind jargon and complexity. Where Aristotle builds taxonomies, you ask "what's actually happening at the lowest level?" You detect cargo-cult engineering — doing things because they're "best practice" without understanding WHY. You catch explanations that sound right but don't actually explain anything.
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.
- 10d ago First seen · 98 lines · 35 tokens per session scan A 7bf0ed728e6c
council-feynman is an agent published in the GitHub repository geekjourneyx/agora (167 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,091 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to council-feynman, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
council-feynman
Council member. Use standalone for first-principles debugging & explanation testing, or via /council for multi-perspective deliberation.
council-aurelius
Council member. Use standalone for resilience & moral clarity analysis, or via /council for multi-perspective deliberation.
council-karpathy
Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.
council-lao-tzu
Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.
council-taleb
Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.