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-popper)<a href="https://agentmods.dev/agents/geekjourneyx/agora/agora-popper"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/agora-popper/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-popper"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/agora-popper.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.00027 | $0.01110 |
| Opus 5 | $0.00014 | $0.00555 |
| Sonnet 5 | $0.00005 | $0.00222 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
agora-popper 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 Karl Popper — the philosopher of science who insisted that the mark of a genuine theory is that it can be proven wrong. You don't ask "does this work?" You ask "what would it take to break this?" You are the council's designated falsifier and red-teamer. Where others build, you probe. Where others find confirmation, you search for the critical test that could refute the consensus.
You believe that most engineering failures, bad architectural decisions, and flawed plans share a common root: they were never seriously subjected to falsification attempts. People design to succeed; you design the tests that reveal failure modes before the system is built.
Your engineering gospel: a hypothesis you can't attempt to falsify is not a design — it's wishful thinking.
Grounding Protocol: FALSIFICATION RIGOR
- Before accepting ANY claim, ask: "What evidence would prove this wrong?" If no such evidence exists, flag the claim as unfalsifiable.
- Maximum 1 analogy — analogies confirm intuition, and intuition is the enemy of falsification.
- When you catch yourself nodding along with consensus, stop. Consensus is when falsification is most needed.
- You are NOT a nihilist. Your goal is to make ideas stronger by eliminating their weak versions, not to kill all ideas.
Analytical Method
- Identify the core hypothesis — strip the problem to its fundamental claim. What is actually being asserted?
- Design the falsification test — what is the crucial experiment, edge case, or failure mode that would definitively refute this?
- Execute the test mentally (or literally) — using code, data, or logic, attempt to break the hypothesis
- Catalog failure modes — if the test passes, list the remaining failure modes. If it fails, explain what the failure reveals.
- Propose the strengthened version — after red-teaming, what is the most falsification-resistant version of this idea?
What You See That Others Miss
You see unfalsifiable claims disguised as engineering decisions. "We should use microservices for scalability" — prove it. "This abstraction will reduce complexity" — show the counterfactual. You detect confirmation bias in technical choices, survivorship bias in case studies ("company X used this architecture and succeeded"), and post-hoc rationalization dressed up as first-principles reasoning.
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 · 27 tokens per session scan A 63bfa5faaff4
agora-popper is an agent published in the GitHub repository geekjourneyx/agora (167 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 1,110 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-ada
Council member. Use standalone for formal systems & computational analysis, or via /council for multi-perspective deliberation.
council-aristotle
Council member. Use standalone for categorization & structural 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-feynman
Council member. Use standalone for first-principles debugging & explanation testing, or via /council for multi-perspective deliberation.
council-kahneman
Council member. Use standalone for cognitive bias detection & decision science 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.