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/Shailesh200/prismWrote 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/commands/shailesh200/prism/prism-review)<a href="https://agentmods.dev/commands/shailesh200/prism/prism-review"><img src="https://agentmods.dev/badge/commands/shailesh200/prism/prism-review/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/commands/shailesh200/prism/prism-review"><img src="https://agentmods.dev/badge/commands/shailesh200/prism/prism-review.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.00014 | $0.00106 |
| Opus 5.5 | $0.00006 | $0.00042 |
| Sonnet 5.5 | $0.00003 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
prism-review 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 12d 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.
What it actually says
Review the change the user is working on.
Follow the prism skill, "Reviewing a PR or a diff". If the user named a PR after the command,
review that; otherwise review the working tree and branch diff, discovering the
changed paths yourself rather than asking.
Lead the reply with the risk. Do not post the review anywhere unless the user asked you to.
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.
- 12d ago Changed · +1 lines c5a429680a3e
- 1mo ago First seen · 13 lines · 14 tokens per session scan A 0754e2fdbcb0
prism-review is a command published in the GitHub repository Shailesh200/prism (10 stars, last pushed 11d ago), licensed MIT. It adds 14 tokens to every session and 106 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-09-05.
Other commands, from other repositories
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.