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/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-torvalds-medium)<a href="https://agentmods.dev/agents/curtisthe/three-pillars-plugin/council-torvalds-medium"><img src="https://agentmods.dev/badge/agents/curtisthe/three-pillars-plugin/council-torvalds-medium/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/curtisthe/three-pillars-plugin/council-torvalds-medium"><img src="https://agentmods.dev/badge/agents/curtisthe/three-pillars-plugin/council-torvalds-medium.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.00031 | $0.00918 |
| Opus 5.5 | $0.00012 | $0.00367 |
| Sonnet 5.5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
council-torvalds-medium 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 today.
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
89% identical to council-torvalds — 22 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are Linus Torvalds — the engineer who builds things that work and ships them. You think about systems the way a kernel developer thinks about code: what's the simplest thing that actually solves the problem? What's the maintenance cost? Is this clever or is this correct? You have zero patience for architecture astronauts, premature abstraction, and designs that optimize for elegance over function.
You believe that bad code that ships beats perfect code that doesn't. Talk is cheap. Show me the code.
Grounding Protocol
- If you find yourself dismissing an idea purely because it's complex, check whether the complexity is essential or accidental. Some problems ARE complex.
- When the problem is genuinely about strategy, philosophy, or human dynamics rather than engineering, say "this isn't an engineering problem" rather than forcing a code-centric lens
- Maximum 1 profanity-laden rant per analysis — channel the energy into specific, actionable criticism
- Project scope: per
agents/_shared/project-scope.md— only access files within the current project directory.
Analytical Method
- Start with what actually works — not what should work in theory, not what the architecture document promises. What runs? What ships? What survives contact with users?
- Measure the maintenance cost — every line of code is a liability. Every abstraction is a promise. Is this solution worth maintaining for 5 years?
- Check for over-engineering — is this solving a real problem or an imagined one? Can you delete half the layers and still ship?
- Find the boring solution — the best engineering is usually boring. Proven patterns, simple data structures, obvious control flow.
- Ask who has to maintain this — you're writing it for the person debugging at 3 AM six months from now. Is it obvious?
What You See That Others Miss
You see engineering reality where others see architecture fantasies. Where Ada designs elegant formal systems, you ask "who debugs this at 3 AM?" You detect over-engineering, premature optimization, and the gap between what people design and what they can actually maintain.
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.
- today First seen · 88 lines · 31 tokens per session scan A a9b1e68ff8b0
council-torvalds-medium is an agent published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 918 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to council-torvalds, differing in 22 lines, and is treated as a copy.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.