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/rikdc/ai-skillsWrote 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/rikdc/ai-skills/triage)<a href="https://agentmods.dev/commands/rikdc/ai-skills/triage"><img src="https://agentmods.dev/badge/commands/rikdc/ai-skills/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.00017 | $0.00561 |
| Opus 5 | $0.00009 | $0.00280 |
| Sonnet 5 | $0.00003 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/triage — PR Review Comment Triage
Triage all unresolved review comments on a pull request. Classifies each comment, decides whether to accept or reject, and takes action.
Usage
/triage # Triage current branch's PR
/triage 123 # Triage PR #123
/triage --dry-run # Preview without acting
/triage --no-resolve # Skip resolving handled threads
Workflow
Execute the triage-reviews skill with the provided arguments.
Use the triage-reviews skill to process the PR review comments. Pass through all arguments from $ARGUMENTS.
Steps
-
Identify the target PR
- If
$ARGUMENTScontains a number or URL, use that PR - Otherwise, run
gh pr view --json number,url,titlefor the current branch
- If
-
Fetch review comments
- Get all review comments via
gh api repos/{owner}/{repo}/pulls/{number}/comments - Get review summaries via
gh api repos/{owner}/{repo}/pulls/{number}/reviews - Get the PR diff for code context via
gh pr diff
- Get all review comments via
-
Classify each comment into: security, correctness, error-handling, performance, design, testing, style, nit, praise, or question
-
Evaluate each comment against the actual code and project conventions:
- Accept: Real issues, valid improvements aligned with project standards
- Reject: Contradicts conventions, subjective preference, misunderstands intent
- Acknowledge: Praise (thank), questions (answer)
-
Present summary table with proposed actions grouped by decision
-
Wait for user confirmation (unless
--dry-run) -
Execute actions:
- Accepted: thumbsup reaction + create beads issue with context and PR comment link
- Rejected: post respectful reply explaining why, citing conventions, then resolve the thread
- Praise: post thank-you reply, then resolve the thread
- Questions: post answer, then resolve the thread (unless uncertain)
-
Report completion with counts of actions taken
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 · 58 lines · 17 tokens per session scan A ba2c5dc59f5f
triage is a command published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 2d ago), licensed MPL-2.0. It adds 17 tokens to every session and 561 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
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.