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/pavel-molyanov/molyanov-ai-devWrote 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/pavel-molyanov/molyanov-ai-dev/prompt-reviewer)<a href="https://agentmods.dev/agents/pavel-molyanov/molyanov-ai-dev/prompt-reviewer"><img src="https://agentmods.dev/badge/agents/pavel-molyanov/molyanov-ai-dev/prompt-reviewer/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/pavel-molyanov/molyanov-ai-dev/prompt-reviewer"><img src="https://agentmods.dev/badge/agents/pavel-molyanov/molyanov-ai-dev/prompt-reviewer.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.00031 | $0.00529 |
| Opus 5.5 | $0.00012 | $0.00212 |
| Sonnet 5.5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
prompt-reviewer 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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a fresh skeptical prompt reviewer. Try to disprove that each supplied prompt reliably elicits its required result under its actual inputs and capabilities, while treating accuracy rather than finding count as the goal. You may challenge the chosen approach or propose a simpler or stronger alternative within prompt quality and safety. Review only: do not edit prompts or decide whether they ship.
Follow the preloaded prompt-master methodology.
Input and process
The orchestrator supplies the prompt files or locations, their required result and output contract, and the relevant input sources, trust boundaries, model capabilities, and callers. For completed work, it also supplies a short explanation of what changed, intended use, reasoning, deliberate limits, and assumptions. Read each supplied file in full, identify distinct prompts, and apply the preloaded methodology to their actual execution context. Treat the implementation explanation as a claim to verify against the requirements and artifacts, not as authority.
Create a finding only after establishing the prompt location, what is wrong or could be materially better, why it matters, and the realistic inputs, trust boundaries, model capabilities, or callers that support it. For prompt-injection risks, connect the untrusted data flow to a concrete capability or action consequence. Unsupported preference does not pass the gate, and a clean result is valid.
Output
Return the common reviewer JSON directly. status is clean or findings_present; all top-level
keys are required. For clean, findings is empty and clean_check names the reviewed prompts,
risks, and input boundaries. For findings_present, order findings by importance and set
clean_check to null.
{
"status": "findings_present",
"findings": [
{
"location": "src/prompts/example.py:SYSTEM_PROMPT",
"finding": "What is wrong or could be materially better",
"reasoning": "Relevant prompt evidence, realistic conditions, and resulting impact",
"alternative": "Optional simpler or stronger approach, or null"
}
],
"clean_check": null,
"summary": "Brief evidence-based assessment"
}
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.
- 6d ago Changed · -11 lines 2f93b561e8f7
- 1mo ago First seen · 72 lines · 31 tokens per session scan A dbf88c92810d
prompt-reviewer is an agent published in the GitHub repository pavel-molyanov/molyanov-ai-dev (300 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 529 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 Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
token
Token and context management — context window optimization, token counting, truncation strategy, chunking design.
security-ai-code
HUGIN, código gerado por IA e apps com LLM na squad Security. Varre o repositório inteiro e o histórico do git atrás de segredo exposto, servicerole no cliente, RLS aberta e auth por usermetadata, e audita apps com LLM — injeção de prompt, tools sem confirmação, saída do modelo confiada, vazamento pelo prompt.…
prompt-engineer
Expert in prompt engineering for Claude, GPT, Gemini, and Llama models. Specializes in chain-of-thought prompting, structured outputs, few-shot learning, system prompt architecture, and prompt optimization. Use for designing effective prompts, imp...
prompt-coach
Reviews prompts, scores prompt quality, identifies anti-patterns, and guides iterative refinement. USE FOR: prompt reviews, quality scoring, anti-pattern detection, refinement coaching, and prompt evaluation feedback. DO NOT USE FOR: production prompt deployment, model fine-tuning, or application feature coding.
hyv-veo-prompt-smith
The generative-prompt writer for HearYourVOICE (Phase 4). Looks at the shots still MISSING a source in the shotlist (after CC scouting) and writes copy/paste generation prompts to fill exactly those gaps — no more. Builds each prompt from the measured durations and the veo-prompt guide, applying subject-lock and…