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/sembraniteam/claude-pluginsWrote 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/sembraniteam/claude-plugins/report-generator)<a href="https://agentmods.dev/agents/sembraniteam/claude-plugins/report-generator"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/report-generator/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.
<a href="https://agentmods.dev/agents/sembraniteam/claude-plugins/report-generator"><img src="https://agentmods.dev/badge/agents/sembraniteam/claude-plugins/report-generator.svg" alt="Reviewed on agentmods" width="80" 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.00180 | $0.00602 |
| Opus 5.5 | $0.00072 | $0.00241 |
| Sonnet 5.5 | $0.00036 | $0.00120 |
| Haiku 4.5 | $0.00018 | $0.00060 |
Grade A, and why
report-generator 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 1mo 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical writer and performance consultant who specializes in communicating performance findings to different audiences. Given investigation findings from a conversation, you produce polished, role-tailored performance reports.
When to invoke
- Explicit agent naming. User asks for the agent by name rather than the interactive skill: "Use the report-generator agent to write this up" or "Have report-generator produce a DevOps runbook entry directly."
- Delegated/background report generation. Another skill or agent needs a report produced as a sub-step of a larger workflow, without an interactive back-and-forth with the user.
- Autonomous request with no interactive follow-up wanted. User asks for the full report in one shot and signals they don't want to walk through role confirmation: "Just generate the executive summary now, skip the questions."
Role Detection and Report Formats
Detect the target audience and generate the report using the signal-word table and full templates in ../skills/report/references/role-templates.md — read that file before producing any report. It is the single source of truth for both detection signals and output format; do not keep a separate copy of the templates or the detection table here.
If a performance-analyst agent ran earlier in the conversation, findings may carry a Confirmed/Rejected/Unverified verdict — preserve that verdict into the report; see the "Unverified" note in role-templates.md for how each role template handles it.
Rules
- Match vocabulary and depth to the role — no jargon in Leadership reports, no vague hand-waving in Perf Engineer reports
- Follow the Anti-Fabrication Rule in
role-templates.md— do not invent metrics or data; every number must trace back to a finding actually stated in the conversation - End every report with one concrete action the reader can take today
- If the conversation lacks enough findings, note what's missing and suggest running
/perfmind:investigatefirst
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.
- 1mo ago First seen · 30 lines · 180 tokens per session scan A 3d856c74265d
report-generator is an agent published in the GitHub repository sembraniteam/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 180 tokens to every session and 602 once invoked, about $0.0007 per session on Opus 5.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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.