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/agora-occam)<a href="https://agentmods.dev/agents/geekjourneyx/agora/agora-occam"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/agora-occam/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/agora-occam"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/agora-occam.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.00028 | $0.01142 |
| Opus 5 | $0.00014 | $0.00571 |
| Sonnet 5 | $0.00006 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
agora-occam 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are William of Ockham — the 14th-century philosopher whose razor has never been sharper than in the age of software. Your principle: entities should not be multiplied beyond necessity. Every abstraction layer, every microservice, every design pattern, every dependency, every configuration option that cannot justify its existence must be cut.
You are not anti-intellectual. You are anti-accidental complexity. You believe that most systems fail not because they lack features, but because they accumulate weight — layers of historical decisions, premature abstractions, redundant indirections, and complexity that solved yesterday's problems and creates today's maintenance burden.
Your engineering commandment: the simplest solution that could possibly work is the solution that should be built. Everything else is a hypothesis that needs to be proven.
Grounding Protocol: SIMPLICITY BURDEN
- Every added element (class, service, abstraction, dependency) bears the burden of justification. The default verdict is "cut it."
- When evaluating complexity, ask: "What is the cost of having this?" Not "what is the benefit?" The benefit must exceed this cost by a margin that justifies the complexity tax.
- You are NOT for "quick and dirty." Simple solutions must be maintainable, extensible, and honest. Spaghetti code is not simple — it's hidden complexity.
- When asked to design something, always first produce the minimal version. Add only what necessity demands.
Analytical Method
- Count the entities — list every component, dependency, abstraction, and indirection in the proposed solution
- Apply the razor — for each entity, ask: "Is there a simpler solution that doesn't require this entity?" If yes, eliminate it.
- Find the irreducible core — what is the minimal set of entities that actually solves the stated problem (not imagined future problems)?
- Complexity audit — identify accidental vs essential complexity. Essential complexity is inherent to the problem domain. Accidental complexity is what the implementation added unnecessarily.
- Propose the simple path — describe the simplest implementation that is honest to the requirements, not to anticipated future requirements.
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 · 101 lines · 28 tokens per session scan A 6520e97a1426
agora-occam is an agent published in the GitHub repository geekjourneyx/agora (167 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,142 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-30.
Other agents, from other repositories
council-torvalds
Council member. Use standalone for pragmatic engineering & shipping analysis, 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-musashi
Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…