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/triage)<a href="https://agentmods.dev/commands/mjmorales/claude-prove/triage"><img src="https://agentmods.dev/badge/commands/mjmorales/claude-prove/triage.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.00016 | $0.01067 |
| Opus 5 | $0.00008 | $0.00534 |
| Sonnet 5 | $0.00003 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
triage 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 7d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Issues: $ARGUMENTS
Review and triage open issues on the prove plugin repository. This is a project-local command for maintainers — it does not ship with the plugin.
Instructions
Step 0: Guard — verify context
- Verify
gh auth statussucceeds. If not, guide the user to authenticate. - This command is for plugin maintainers. All operations target
mjmorales/claude-provevia--repoflag; no local repo check needed.
Step 1: Fetch issues
If $ARGUMENTS is a number, fetch that single issue:
gh issue view $ARGUMENTS --repo mjmorales/claude-prove --json number,title,body,labels,createdAt,author,comments
If $ARGUMENTS is a label (e.g., "bug", "enhancement"), filter:
gh issue list --repo mjmorales/claude-prove --label "$ARGUMENTS" --state open --json number,title,labels,createdAt,author --limit 25
Otherwise, fetch all open issues:
gh issue list --repo mjmorales/claude-prove --state open --json number,title,labels,createdAt,author --limit 25
Step 2: Present overview
Display issues in a table:
Open Issues (N total)
# | Title | Labels | Age | Author
---|-------------------------------------|-------------|------|--------
12 | /prove:update runs in plugin dir | bug | 2d | user1
11 | Add coding standards reference | enhancement | 5d | user2
Step 3: Triage each issue
For each issue (or the single requested issue), read the full body and comments, then assess:
- Assess clarity: Is the issue description clear enough to act on? Are reproduction steps or acceptance criteria present?
- Classify severity:
critical— blocks core functionality (init, update, orchestrator)high— breaks a specific command/skillmedium— incorrect behavior with workaroundlow— cosmetic, docs, nice-to-have
- Security check: If the issue involves credential exposure, injection, or unauthorized access, apply the
securitylabel. Do NOT discuss reproduction details in public comments. - Identify affected components: Which commands, skills, agents, or tools are involved? Use directory names as component labels (e.g.,
commands,agents,packages/cli/src/topics/cafi). - Estimate scope: quick fix (< 30 min), medium task, or needs planning.
- Check for duplicates: Search existing open issues for similar reports before accepting.
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.
- 7d ago First seen · 118 lines · 16 tokens per session scan A e7a45d2947b0
triage is a command published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 28d ago), licensed MIT. It adds 16 tokens to every session and 1,067 once invoked, about $0.0001 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.