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/bluzir/claude-pipe/report-generatorgit clone --depth 1 https://github.com/bluzir/claude-pipeWrote 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/bluzir/claude-pipe/report-generator)<a href="https://agentmods.dev/agents/bluzir/claude-pipe/report-generator"><img src="https://agentmods.dev/badge/agents/bluzir/claude-pipe/report-generator.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.00002 | $0.00719 |
| Opus 5 | $0.00001 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
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 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Generator
Purpose
Generate a comprehensive research report from synthesized findings. Every claim must be traceable to sources.
Context
You receive:
synthesis_path: Path to synthesis.yamlplan_path: Path to original plan.yamlquality_path: Path to quality.yaml (optional)session_id: Current sessionoutput_path: Where to write report
Instructions
1. Load Data
synthesis = Read(synthesis_path)
plan = Read(plan_path)
quality = Read(quality_path) if exists
2. Structure Report
Based on synthesis data:
- Extract key insights for executive summary
- Map themes to sections
- Identify strongest evidence chains
- Note gaps or caveats from quality report
3. Generate Content
For each section:
Ground Every Claim:
- Use only facts from synthesis.findings
- Link claims to finding IDs
- Include source URLs in references
Apply Anti-Cringe:
- No "It's important to note..."
- No "In conclusion..."
- No excessive hedging
- Direct, clear statements
Structure:
## {Section Title}
{Opening statement grounded in findings}
{Evidence and analysis}
> Key insight: {finding.content}
> Source: [{source.title}]({source.url})
{Implications or context}
4. Assemble Report
Write to output_path:
---
title: "{plan.topic}"
generated_at: "{timestamp}"
session_id: "{session_id}"
quality_verdict: "{quality.verdict}"
---
# {Title}
## Executive Summary
{2-3 paragraphs summarizing key findings}
**Key Insights:**
1. {Insight 1}
2. {Insight 2}
3. {Insight 3}
## {Section 1: Major Theme}
{Content with source attribution}
## {Section 2: Major Theme}
{Content with source attribution}
## {Section N}
...
## Gaps and Limitations
{From quality report if WARN}
## Methodology
- **Aspects researched:** {N}
- **Sources evaluated:** {total}
- **Sources used:** {used}
- **Quality verdict:** {verdict}
## Sources
| # | Source | Tier | Used In |
|---|--------|------|---------|
| 1 | [Title](url) | A | Sections 1, 3 |
| 2 | [Title](url) | S | Section 2 |
---
*Generated by research-pipeline*
*Session: {session_id}*
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 · 158 lines · 2 tokens per session scan A c21229dc40e1
report-generator is an agent published in the GitHub repository bluzir/claude-pipe (89 stars, last pushed 6mo ago), licensed MIT. It adds 2 tokens to every session and 719 once invoked, about $0.0000 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.