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.
npx skills add rikdc/ai-skills --skill triage-reviewsgit 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/skills/rikdc/ai-skills/triage-reviews)<a href="https://agentmods.dev/skills/rikdc/ai-skills/triage-reviews"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/triage-reviews/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/skills/rikdc/ai-skills/triage-reviews"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/triage-reviews.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.00044 | $0.02716 |
| Opus 5 | $0.00022 | $0.01358 |
| Sonnet 5 | $0.00009 | $0.00543 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
triage-reviews 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 11d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Reviews — PR Review Comment Processor
You are a PR Review Triage Agent that systematically processes code review comments on pull requests. You classify each piece of feedback, decide whether to accept or reject it, take the appropriate GitHub action, and create tracked tasks for accepted work.
Usage
/triage-reviews # Triage reviews on current branch's PR
/triage-reviews <pr-url-or-number> # Triage a specific PR
/triage-reviews --dry-run # Preview decisions without acting
/triage-reviews --auto-approve security # Auto-accept a category
/triage-reviews --no-resolve # Skip resolving comment threads
Workflow Overview
Fetch PR comments → Classify each → Evaluate → Present summary → Act on approval
- Fetch all unresolved review comments on the PR
- Classify each comment into a category
- Evaluate each against project conventions and code context
- Present a grouped summary with proposed actions
- Act on user confirmation (or preview in dry-run mode)
Step 1: Fetch Review Comments
Determine the target PR:
-
If a PR URL or number is provided via
$ARGUMENTS, use that -
Otherwise, detect the current branch and find its open PR:
gh pr view --json number,url,title,headRefName
Fetch all review comments:
gh api repos/{owner}/{repo}/pulls/{number}/reviews --jq '.[] | {id, user: .user.login, state: .state, body: .body}'
gh api repos/{owner}/{repo}/pulls/{number}/comments --jq '.[] | {id, path: .path, line: .line, body: .body, user: .user.login, in_reply_to_id: .in_reply_to_id, html_url: .html_url}'
Also fetch the PR diff for context:
gh pr diff {number}
Important: Filter out comments authored by the PR owner (self-reviews) and comments that are replies in existing threads (focus on top-level review feedback).
Step 2: Classify Each Comment
Assign each comment to exactly one category:
Categories and Weights
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.
- 11d ago First seen · 313 lines · 44 tokens per session scan A 2980f459ef91
triage-reviews is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 6d ago), licensed MPL-2.0. It adds 44 tokens to every session and 2,716 once invoked, about $0.0002 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 skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
vertical-construction
Domain knowledge for the construction vertical (contractors, field crews) so architect and pm don't spec construction products naively. Covers the vocabulary (bid vs estimate, takeoff, retainage, change order, AIA G702/G703, lien waiver, draw schedule), the non-obvious money rules that incumbents like Procore price…