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/mjmorales/claude-proveWrote 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/mjmorales/claude-prove/review-ui)<a href="https://agentmods.dev/commands/mjmorales/claude-prove/review-ui"><img src="https://agentmods.dev/badge/commands/mjmorales/claude-prove/review-ui/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/mjmorales/claude-prove/review-ui"><img src="https://agentmods.dev/badge/commands/mjmorales/claude-prove/review-ui.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.00022 | $0.01290 |
| Opus 5 | $0.00011 | $0.00645 |
| Sonnet 5 | $0.00004 | $0.00258 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade C, and why
review-ui scanned grade C with 2 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 9d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
> `claude-prove` CLI not found on PATH. Install via `curl -fsSL https://raw.githubusercontent.com/mjmorales/claude-prove/main/scripts/install.sh | bash`. Dev-mode users: alias or symlink `claude-prove` to your working-tr Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> `claude-prove` CLI not found on PATH. Install via `curl -fsSL https://raw.githubusercontent.com/mjmorales/claude-prove/main/scripts/install.sh | bash`. Dev-mode users: alias or symlink `claude-prove` to your working-tr How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review UI
Drive the prove review UI through the in-process daemon. claude-prove review-ui serve starts, stops, queries, and restarts a detached loopback server; its pidfile and log live under ~/.claude-prove/review-ui/.
Default (no arguments): serve start → read the resolved port from its stdout → open the browser at that port.
Precondition
Check this first. On failure, print the message and stop — do nothing else.
claude-prove on PATH: run command -v claude-prove >/dev/null. If it is missing, print:
claude-proveCLI not found on PATH. Install viacurl -fsSL https://raw.githubusercontent.com/mjmorales/claude-prove/main/scripts/install.sh | bash. Dev-mode users: alias or symlinkclaude-proveto your working-tree entry point.
Arguments
Parse $ARGUMENTS:
--stop—serve stop, then exit. No start, no browser.--status—serve status, print the JSON, then exit. No start, no browser.--restart—serve restartinstead ofserve start.--port <N>— pin the listen port, bypassing machine-config resolution and the busy-port scan.--no-open— start (or restart) but do not open a browser.
Empty $ARGUMENTS runs the default start-and-open flow.
Flow
Stop
When --stop is set:
claude-prove review-ui serve stop
Report the outcome and exit.
Status
When --status is set:
claude-prove review-ui serve status
status prints {"running":<bool>,"pid":<int|null>,"port":<int>} on stdout. Echo it, summarize whether the daemon is running, and exit.
Start or restart
Pick the verb from the arguments — serve restart when --restart is set, otherwise serve start. Append --port <N> only when the user passed it.
claude-prove review-ui serve start # or: serve restart
start resolves the repo root from the current directory, resolves the port (the machine-global ~/.claude-prove/config.json::review_ui_port, then an upward scan past any busy port — a bump is warned on stderr), resolves the web bundle in the parent (a missing bundle warns on stderr and boots API-only), spawns the detached loopback child, and polls /api/health until it answers. On success it prints {"running":true,"pid":<int>,"port":<int>} on stdout. restart stops any recorded daemon first, then runs the same start path.
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.
- 9d ago First seen · 104 lines · 22 tokens per session scan C fc106f8fbcbc
review-ui is a command published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 29d ago), licensed MIT. It adds 22 tokens to every session and 1,290 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.