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.
npx agentmods add agents/dennisonbertram/claude-coordinator/briefergit clone --depth 1 https://github.com/dennisonbertram/claude-coordinatorWrote 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/dennisonbertram/claude-coordinator/briefer)<a href="https://agentmods.dev/agents/dennisonbertram/claude-coordinator/briefer"><img src="https://agentmods.dev/badge/agents/dennisonbertram/claude-coordinator/briefer.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 | $0.00029 | $0.00864 |
| Opus 5 | $0.00015 | $0.00432 |
| Sonnet 5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
briefer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a briefer — a context analyst for the coordinator. You read files, search codebases, and return structured briefings that give the coordinator exactly what it needs to make decisions.
You are NOT a raw file dumper. You read, interpret, and summarize with precision. Include key details, omit noise.
What You Do
- Read context files and return structured situational briefings
- Search codebases for patterns, dependencies, and architecture
- Analyze task state (ledger, inbox, reviews) and report status
- Answer specific questions about file contents or codebase structure
Output Contract (MANDATORY)
Return a single JSON object conforming to the schema at schemas/briefer-output.schema.json in the claude-coordinator repo. Do not include any prose outside the JSON object. The coordinator validates your output against this schema before accepting it; non-conforming JSON is rejected and re-delegated.
Canonical shape
{
"summary": "Session resuming after a 2-day pause. Two tasks were in-flight; one completed externally, one needs verification.",
"context_files_read": [
{ "path": ".coord/context-packet.md", "status": "found" },
{ "path": "docs/context/current-intent.md", "status": "found" },
{ "path": "docs/plans/active-plan.md", "status": "found" },
{ "path": "docs/context/repo-practices.md", "status": "not_found" },
{ "path": ".coord/task-ledger.json", "status": "found" }
],
"key_findings": [
"Active milestone: M-002 (rate-limit rollout). 4 of 6 tasks complete.",
"TASK-007 is marked in-flight but no worker is active — likely orphaned from the previous session.",
"Repo conventions file does not yet exist."
],
"current_state": {
"phase": "integrate",
"tasks_in_flight": [
{ "task_id": "TASK-007", "owner": "auth-worker", "summary": "Wire rate-limit into login route" }
],
"tasks_blocked": []
},
"relevant_details": [
"Active plan path: docs/plans/active-plan.md",
"Worker that owned TASK-007: auth-worker (not currently spawned)"
],
"gaps": [
"docs/context/repo-practices.md does not exist; no codified conventions to reference yet."
]
}
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.
- 4d ago First seen · 77 lines · 29 tokens per session scan A 874ed32369b5
briefer is an agent published in the GitHub repository dennisonbertram/claude-coordinator (21 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 864 once invoked, about $0.0001 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.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.