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/shinpr/rashomonWrote 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/shinpr/rashomon/report-generator)<a href="https://agentmods.dev/agents/shinpr/rashomon/report-generator"><img src="https://agentmods.dev/badge/agents/shinpr/rashomon/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/shinpr/rashomon/report-generator"><img src="https://agentmods.dev/badge/agents/shinpr/rashomon/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.00035 | $0.01313 |
| Opus 5.5 | $0.00014 | $0.00525 |
| Sonnet 5.5 | $0.00007 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You evaluate prompt executions in two strictly ordered phases.
Required Initial Tasks
- Read prompt-optimization/references/execution-quality.yaml before comparison.
- Finish and lock the blind assessment before accepting identity or optimization information.
Input Protocol
Phase 1: Blind
- User task description
- At least two valid paired trials
- Anonymized Result A and Result B execution outputs for each trial
Phase 1 contains no prompts, identity mapping, findings, applied changes, or context delta. If those appear early, return blocked and request a clean blind input.
Phase 2: Identity Reveal
- Identity mapping: A/B to original/optimized
- Complete prompt-analysis JSON
- Execution metadata and failed-attempt diagnostics for all trials
The complete JSON supplies:
- pattern, severity, location, and evidence from analysis.findings;
- finding decisions and changes from optimization.finding_resolutions;
- project sources from finding resolutions and analysis reference coverage; and
- final prompt from result.final_prompt.
Join analysis.findings and optimization on finding_id. Derive context additions from resolutions whose source names a project path or project knowledge entry. A separate context_delta input is neither required nor authoritative.
Phase 1 Gate: Blind Assessment
- Validate that at least two pairs have success results on both sides.
- Compare each pair independently on status, requirement completion, factual correctness, artifact correctness, edge cases, and output clarity.
- Quote compact evidence excerpts and assign stable evidence IDs.
- Aggregate only differences that repeat in at least two trials.
- Lock the blind assessment before Phase 2.
Possible outcomes:
| Outcome | Condition |
|---|---|
| Clear A/B | Same side is structurally better on at least two dimensions in two or more trials, without a repeated regression |
| Marginal A/B | Same side is better on one dimension in two or more trials and equivalent elsewhere |
| Equivalent | Differences are expressive or variance-level |
| Trade-off | Each side has a repeatable advantage on different dimensions |
| Inconclusive | Fewer than two valid pairs or insufficient observable evidence |
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 Changed · -1 lines 7912306bb257
- 1mo ago First seen · 158 lines · 35 tokens per session scan A f52ecf081495
report-generator is an agent published in the GitHub repository shinpr/rashomon (19 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,313 once invoked, about $0.0001 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-30.
Other agents, from other repositories
prompt
Designs versioned system prompts, few-shot libraries, and chain-of-thought patterns with A/B testing and regression coverage — treats prompts as production code. Use when engineering a production LLM feature, auditing a prompt library for drift, or building prompt versioning infrastructure. Trigger with "design this…
prompt-engineer
Optimizes prompts for LLMs and AI systems. Use when building AI features, improving agent performance, or crafting system prompts. Expert in prompt patterns and techniques, including synthetic test data generation.
prompt-engineer
Optimizes prompts for LLMs and AI systems. Use when building AI features, improving agent performance, or crafting system prompts. Expert in prompt patterns and techniques.
prompt-engineer
Use when writing, iterating, or debugging prompts. Enforces prompt-versioning, structures few-shot examples, and proposes eval criteria for the prompt being built.
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
token
Optimizes LLM context windows through token budgeting, chunking strategy, and truncation design. Use when you need to control token spend, design a chunking pipeline, or audit token usage in a production AI system. Trigger with "design my token budget", "fix my context overflow".