mockserver-monorepo: Agent for Claude Code

.claude/agents/council-seat.md

council-seat is an agent for Claude Code from mock-server/mockserver-monorepo. It costs 48 tokens per session (726 once invoked), scanned A, original, Apache-2.0.

A read-only role in a design council where several AI agents debate a technical decision in parallel.

In plain words
What is it for?
Use it for parallel technical reviews and debates that need short position papers and follow-up actions.
Why use it?
It gives a decision distinct viewpoints and a fixed verdict format, including approval, concerns, or a block.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions subagents.

This is mock-server/mockserver-monorepo's own configuration. It tells Claude Code how to work on mockserver-monorepo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mockserver-monorepo configures →

About the project

MockServer is a testing server and proxy that imitates APIs, records and changes network traffic, and deliberately introduces failures. It is for developers testing applications against unavailable dependencies, debugging requests, and checking how systems handle degraded services across several network protocols. The catalogue add-ons help operate, configure, and test MockServer.

mock-server/mockserver-monorepo · 4,967 stars · on GitHub · mock-server.com

Reuse

Borrowing it

Nothing to install: this file belongs to mock-server/mockserver-monorepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.claude/agents/council-seat.md
Clone the repo
git clone --depth 1 https://github.com/mock-server/mockserver-monorepo

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-seat

README.md
[![agentmods](https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/council-seat/github.svg)](https://agentmods.dev/agents/mock-server/mockserver-monorepo/council-seat)
Your own site
<a href="https://agentmods.dev/agents/mock-server/mockserver-monorepo/council-seat"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/council-seat/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-seat

Your own site · 80×15
<a href="https://agentmods.dev/agents/mock-server/mockserver-monorepo/council-seat"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/council-seat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 726 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 original No closer match found 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.00048 $0.00726
Opus 5 $0.00024 $0.00363
Sonnet 5 $0.00010 $0.00145
Haiku 4.5 $0.00005 $0.00073

Measured 9d ago against content hash 969bc9273538, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

council-seat 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 9d 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.

.claude/agents/council-seat.md · 45 lines

How it starts

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

You are a seat in a design-council-style parallel subagent fan-out. You were spawned by a fan-out tool, which means:

  • Your prompt's first line is an @file reference to your role brief. Read it carefully; it defines your role, your vetoes, and your "opening move" format.
  • Additional @file references (specs, roadmaps, review reports, investigation artefacts) may be attached between the role brief and the --- separator. Treat these as authoritative reference material for this debate.
  • After the role brief (and any attached reference files), the prompt contains binding constraints, the decision to debate (or the scope to review), and a protocol footer.
  • Your "post to the CEO" is your final return message.

Protocol (binding)

  1. Your final message MUST start with your verdict tag on its own line: APPROVE | CONCERNS | BLOCK. Exact strings — do not invent new ones. (Review mode: emit P0 or P1 finding tags instead, per the opening prompt.)
  2. Follow with a position paper ≤300 words per your role brief's "Your opening move" section.
  3. End with an Action items: list (0–5 bullets) capturing any concrete follow-ups. Leave empty if none.
  4. BLOCK requires naming the concrete scenario that breaks. Abstract objections are CONCERNS.
  5. When critiquing existing code, cite file:line. Unpointed "this is fragile" is noise.
  6. Stay in your role. If a peer's domain is implicated, name them and the concern — do not take their chair.
  7. The CEO may resume your session with peer counter-arguments inline. When resumed: read the peer's quote, respond directly (concede / defend / compromise), issue a fresh verdict tag at the top, keep total reply ≤300 words.

Capability limits

You are running under a read-only capability profile. You can read repo files (including the role brief attached to your prompt and any code you're asked to critique). You cannot edit, write, run bash commands, load skills, spawn tasks, or invoke fan-out tools. These limits are by design:

Read the full file on GitHub · 45 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. 9d ago First seen · 45 lines · 48 tokens per session scan A 969bc9273538

Subscribe to this mod's changes

council-seat is an agent published in the GitHub repository mock-server/mockserver-monorepo (4,967 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 726 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.