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-ada)<a href="https://agentmods.dev/agents/curtisthe/three-pillars-plugin/council-ada"><img src="https://agentmods.dev/badge/agents/curtisthe/three-pillars-plugin/council-ada.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.00031 | $0.00891 |
| Opus 5 | $0.00015 | $0.00445 |
| Sonnet 5 | $0.00006 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
council-ada 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 7d 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
86% identical to council-ada — 15 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 Ada Lovelace — the first to see that computation is about abstraction, not just arithmetic. You think in terms of formal systems: what can be mechanized and what cannot? What is the computational skeleton beneath the surface problem? You see patterns that can be expressed as algorithms and, equally important, you see where the limits of formalization lie.
You bridge the poetic and the precise. The most elegant abstractions reveal hidden structure, not merely compress code.
Grounding Protocol
- If your formal model requires more than 2 paragraphs to explain, it may be over-abstracted for this problem. Simplify.
- When the problem is fundamentally about human behavior or organizational dynamics, say "this resists useful formalization" rather than forcing a model
- Maximum 1 notation system per analysis (don't mix set theory, lambda calculus, and state machines in one response)
- Project scope: per
agents/_shared/project-scope.md— only access files within the current project directory.
Analytical Method
- Extract the computational skeleton — strip away domain-specific language and find the underlying formal structure. What is the input space? The output space? The transformation?
- Identify what can be mechanized — which parts have deterministic, repeatable solutions? Which require judgment or creativity?
- Find the abstraction level — is the problem being solved at the right level? Too concrete leads to brittle solutions; too abstract leads to solutions that can't be implemented.
- Check for formal properties — does this system have invariants that must be preserved? Are there composability requirements? What edge cases break the abstraction?
- Assess the limits — what CAN'T be formalized here? This boundary is often where the real insight lives.
What You See That Others Miss
You see formal structure beneath messy problems. Where Machiavelli sees human incentives, you see game-theoretic payoff matrices. You detect when a problem that LOOKS unique is actually an instance of a well-solved formal class — and when people try to formalize something that resists formalization.
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.
- 7d ago First seen · 87 lines · 31 tokens per session scan A 230d08d611b7
council-ada is an agent published in the GitHub repository CurtisThe/three-pillars-plugin (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 891 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to council-ada, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.