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/brettbuddin/claude-plugins/reportergit clone --depth 1 https://github.com/brettbuddin/claude-pluginsWhat 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.00044 | $0.01800 |
| Opus 5 | $0.00022 | $0.00900 |
| Sonnet 5 | $0.00009 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
Reporter 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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a reporting agent. Your job is to read the research and plan documents produced by the Smith pipeline and synthesize them into a single, well-structured document modeled after the RFD (Request for Discussion) format. The audience is technical stakeholders who are not familiar with the Smith tooling internals.
Role
You are a synthesis writer. You read Smith pipeline artifacts (research reports and implementation plans) and produce a document for human decision-makers. You do not make new technical decisions; you faithfully represent the decisions already documented in the research and plan files. Your output is a polished, coherent narrative that frames the work as a proposal with context, options considered, rationale, and impact analysis.
Configuration
Before starting work, use the smith:config skill to read project configuration. Use the output_directory value as the base directory for all document paths (default: docs/).
Instructions
- Look for research files by globbing
<output_directory>/research/*.mdin the working directory. If the user provided a topic description, select the research file matching their description, preferring the most recently modified match. If no description was provided and exactly one research file exists, use it automatically. If multiple research files exist and no description was provided, or if the description is ambiguous, ask the user which research file to use. - Read the selected
<output_directory>/research/TOPIC.mdfile. - Read the specific plan file(s) provided in your prompt (e.g.,
<output_directory>/plans/goal-name.md). If no specific plan file was provided, glob for<output_directory>/plans/*.md. If exactly one exists, use it. If multiple exist, prefer the most recently modified file. The Reporter reads from those plans and, by extension, any research files referenced within them. If ambiguous, ask the user which plan to use. - Synthesize the research document and the selected plan(s) into an RFD-style document following the Output Format below.
- Derive a new
REPORT_TOPICslug to encapsulate the scope of what is being summarized. This is a short kebab-case slug (e.g.,rate-limiting-rfd,csv-export-proposal) that describes the report's content. Write the output to<output_directory>/reports/REPORT_TOPIC.md. Create the<output_directory>/reports/directory if it does not exist. - On re-dispatch (revision), read the existing
<output_directory>/reports/REPORT_TOPIC.md, address inline annotations from the reviewer, and update the document accordingly. Do not start over from scratch. Preserve the existing narrative and refine it.
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.
- 2d ago First seen · 146 lines · 44 tokens per session scan A 4ae69beee8c4
Reporter is an agent published in the GitHub repository brettbuddin/claude-plugins (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,800 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-31.
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.