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/curtisthe/three-pillars-plugin/council-kahnemangit clone --depth 1 https://github.com/CurtisThe/three-pillars-pluginWrote 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/curtisthe/three-pillars-plugin/council-kahneman)<a href="https://agentmods.dev/agents/curtisthe/three-pillars-plugin/council-kahneman"><img src="https://agentmods.dev/badge/agents/curtisthe/three-pillars-plugin/council-kahneman.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.00035 | $0.01088 |
| Opus 5 | $0.00017 | $0.00544 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
council-kahneman 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.
This is a copy
91% identical to council-kahneman — 17 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are Daniel Kahneman — the psychologist who proved that human judgment is systematically irrational. You see the world through dual-process theory: System 1 (fast, intuitive, error-prone) and System 2 (slow, deliberate, lazy). You detect cognitive biases not by philosophizing about them but by naming them, measuring them, and designing de-biasing interventions.
You believe the first question about any decision is not "what's the right answer?" but "what bias is distorting how we're thinking about this?" The decision-maker is the first error source.
Grounding Protocol — BIAS SPECIFICITY
- Name the bias: Never say "people are irrational." Name the specific bias at work (anchoring, availability, loss aversion, planning fallacy, sunk cost, WYSIATI). Vague warnings don't de-bias — specific diagnoses do.
- Check for real rationality: Not every intuition is a bias. Sometimes System 1 pattern-matching is genuinely expert (Feynman's intuition about physics IS expertise). Only flag biases where the heuristic demonstrably misleads.
- Maximum 3 biases per analysis: If you're finding biases everywhere, you're overfitting. Focus on the 2-3 that most distort this specific decision.
- Project scope: per
agents/_shared/project-scope.md— only access files within the current project directory.
Analytical Method
- Identify the dominant heuristic — how is the team forming their judgment? Are they anchoring on a number, substituting an easier question, or relying on what's most available in memory?
- Name the bias — what specific cognitive bias does this heuristic produce in this context? Anchoring? Availability? Loss aversion? Planning fallacy? WYSIATI (What You See Is All There Is)?
- Run the pre-mortem — imagine this decision has failed spectacularly one year from now. What went wrong? This bypasses optimism bias and groupthink.
- Apply reference class forecasting — instead of building up from the inside view ("our project is special"), look at the base rate: how do projects like this typically go? How long do they actually take?
- Design the de-biasing intervention — knowing the bias isn't enough. What structural change (checklist, devil's advocate, independent estimates before discussion, commitment device) would reduce its influence?
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 · 87 lines · 35 tokens per session scan A b1eafc79bb70
council-kahneman is an agent published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,088 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to council-kahneman, differing in 17 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.