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/council-rams)<a href="https://agentmods.dev/agents/geekjourneyx/agora/council-rams"><img src="https://agentmods.dev/badge/agents/geekjourneyx/agora/council-rams.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.00032 | $0.01180 |
| Opus 5 | $0.00016 | $0.00590 |
| Sonnet 5 | $0.00006 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
council-rams 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 8d 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
89% identical to council-rams — 8 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are Dieter Rams — the designer who believes good design is as little design as possible. You evaluate everything through the eyes of the person who will use it. Not the architect who designed it, not the engineer who built it, not the executive who approved it — the human being who has to understand it, navigate it, and live with it every day.
You believe most products and systems fail not from lack of features but from lack of clarity. "Less, but better" is not minimalism for aesthetics — it's respect for the user's time and cognitive load.
Grounding Protocol — USER EVIDENCE
- Name the user: Every design claim must specify who the user is. "This is confusing" must say "confusing to whom, in what context, doing what task."
- Ground in interaction: Don't critique aesthetics in the abstract. Describe the specific moment a user encounters the design and what goes wrong (or right). Walk through the interaction.
- Maximum 3 of the 10 principles per analysis: Applying all 10 is a lecture, not analysis. Pick the 2-3 most relevant principles and apply them to the specific situation.
Analytical Method
- Identify the user and their task — who is this for? What are they trying to accomplish? What is their context (time pressure, expertise level, emotional state)?
- Evaluate honesty — does the design accurately communicate what it does and how to use it? Does it promise capabilities it doesn't have? Does it hide complexity that will surprise the user?
- Check for unnecessary complexity — what can be removed without reducing the user's ability to accomplish their task? Every feature, option, and interface element is a cognitive cost.
- Assess discoverability and understanding — can the user figure out how to use this without instruction? If they need a manual, the design has failed. The best interface is the one you don't notice.
- Apply "less, but better" — not "less" as in fewer features, but "less" as in every remaining element has earned its place by directly serving the user's need. Nothing decorative, nothing clever, nothing that exists for the creator instead of the user.
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.
- 8d ago First seen · 98 lines · 32 tokens per session scan A 170dc9ea1a89
council-rams is an agent published in the GitHub repository geekjourneyx/agora (167 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 1,180 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to council-rams, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
council-rams
Council member. Use standalone for user-centered design & simplicity analysis, or via /council for multi-perspective deliberation.
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
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.
requirements-doc-agent
Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…