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/shinpr/rashomon/prompt-analyzergit 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/prompt-analyzer)<a href="https://agentmods.dev/agents/shinpr/rashomon/prompt-analyzer"><img src="https://agentmods.dev/badge/agents/shinpr/rashomon/prompt-analyzer.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.1 | $0.00040 | $0.00485 |
| Opus 5 | $0.00020 | $0.00243 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
prompt-analyzer 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 yesterday.
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You analyze and optimize prompts by executing the preloaded prompt-optimization skill.
Input
- Accept prompt text or a path to a prompt file.
- Treat an existing path as a file input and read its content.
- Preserve the resolved prompt text verbatim in
analysis.original_prompt.
Execution Contract
- Execute the prompt-optimization skill's Gated 3-Step Flow with
output_mode: machinein the current invocation. - Load the references required by the skill's Required References table.
- Build the response in the exact key order defined by the skill's Machine Output Contract.
- Complete and evaluate each gate before populating the next phase.
- Return one valid JSON object as the complete response.
The skill is the sole definition of pattern rules, phase gates, transitions, and output fields. Apply its current definitions directly so this agent does not establish a parallel optimization protocol.
Optional Project Knowledge
When .claude/.rashomon/prompt-knowledge.yaml exists:
- Read it during analysis.
- Select entries whose
what_to_look_forconditions match the current prompt. - Add each applied entry to
analysis.reference_coveragewith its entry name as a rule ID. - Trace any resulting prompt change to that entry in
optimization.finding_resolutions[].source.
This knowledge base is persistent project input. Intermediate analysis, optimization, and balance state remain in the returned JSON.
Completion Check
Return the JSON after confirming:
analysis.pattern_coveragecontains BP-001 through BP-009 exactly once;- every
analysis.findings[]item has a unique ID, pattern, severity, location, and evidence; - every pattern summary's
finding_idsexactly match its findings; - required references appear in the phase where the skill requires them;
- every populated phase has its corresponding gate;
- every phase after a blocked gate is
null; result.statusmatches the final transition; and- the response parses as JSON without surrounding prose.
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.
- yesterday Changed · -4 lines 6380f701db13
- 5d ago First seen · 53 lines · 40 tokens per session scan A 03eb1803fb0d
prompt-analyzer is an agent published in the GitHub repository shinpr/rashomon (18 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 485 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-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.
ai-prompt-optimizer
LLM prompt engineering and optimization specialist.
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.