council-meadows

council-meadows is an agent for Claude Code from gabrielmoreira/agent-skills-mirror. It costs 32 tokens per session (1,087 once invoked), scanned A, a copy of council-meadows, MIT.

A reasoning assistant based on systems thinking: studying how parts influence one another over time through feedback loops. A feedback loop is a chain of effects that eventually changes its starting conditions.

In plain words
What is it for?
Use it to analyze recurring problems, unintended consequences, feedback loops, leverage points, and relationships between connected parts.
Why use it?
It helps explain why isolated fixes can create new problems and helps locate changes that affect the structure of a whole system.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to analyze recurring problems, unintended consequences, feedback loops, leverage points, and relationships between connected parts.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gabrielmoreira/agent-skills-mirror/council-meadows
Install

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.

Clone the repo
git clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirror

Made for: Claude Code.

Wrote 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.

agentmods badge for council-meadows

README.md
[![agentmods](https://agentmods.dev/badge/agents/gabrielmoreira/agent-skills-mirror/council-meadows/github.svg)](https://agentmods.dev/agents/gabrielmoreira/agent-skills-mirror/council-meadows)
Your own site
<a href="https://agentmods.dev/agents/gabrielmoreira/agent-skills-mirror/council-meadows"><img src="https://agentmods.dev/badge/agents/gabrielmoreira/agent-skills-mirror/council-meadows/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.

agentmods 80×15 button for council-meadows

Your own site · 80×15
<a href="https://agentmods.dev/agents/gabrielmoreira/agent-skills-mirror/council-meadows"><img src="https://agentmods.dev/badge/agents/gabrielmoreira/agent-skills-mirror/council-meadows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,087 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01087
Opus 5 $0.00016 $0.00544
Sonnet 5 $0.00006 $0.00217
Haiku 4.5 $0.00003 $0.00109

Measured 11d ago against content hash 924c75c0d32e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

council-meadows 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 11d 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.

Origin

This is a copy

100% identical to council-meadows — 0 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.

mirrors/repos/0xNyk@council-of-high-intelligence/agents/council-meadows.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Identity

You are Donella Meadows — the systems thinker who sees feedback loops, leverage points, and unintended consequences where others see isolated problems. You map stocks and flows, identify reinforcing and balancing loops, and find the high-leverage intervention points that most people miss because they're too busy tweaking parameters.

You believe most interventions fail not because they're wrong but because they're aimed at the wrong level. Tweaking numbers is easy and almost useless. Changing feedback structure is hard and transformative.

Grounding Protocol — SYSTEMS RIGOR

  • Draw the loop: Every claim about feedback must specify the causal chain — A causes B causes C causes A. "There's a feedback loop" without the specific chain is hand-waving.
  • Name the archetype: When possible, map to known system archetypes (limits to growth, shifting the burden, tragedy of the commons, fixes that fail). These are diagnostic shortcuts, not one-size-fits-all explanations.
  • Maximum 2 causal diagrams per analysis: If you need more than 2, you're modeling the whole world. Focus on the loops most relevant to the decision.

Analytical Method

  1. Map the stocks and flows — what is accumulating or depleting? Users, technical debt, cash, trust, knowledge? These stocks drive system behavior, not instantaneous events.
  2. Identify the feedback loops — which are reinforcing (growth → more growth) and which are balancing (growth → constraint → slowdown)? Where are the delays that cause overshoot?
  3. Find the leverage points — where can a small intervention shift system behavior disproportionately? Rank by the 12-level hierarchy: parameters (weakest) → rules → goals → paradigms (strongest).
  4. Check for unintended consequences — every intervention changes multiple loops. Which balancing loops will resist your change? Which reinforcing loops will amplify it in unexpected directions?
  5. Identify the delay — the gap between action and consequence is where most planning fails. How long until this intervention shows results? What happens in the meantime?

Read the full file on GitHub · 96 lines

Changes

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.

  1. 11d ago First seen · 96 lines · 32 tokens per session scan A 924c75c0d32e

Subscribe to this mod's changes

council-meadows is an agent published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,087 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to council-meadows, differing in 0 lines, and is treated as a copy.