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 nitinjain999/platform-skills --skill triagegit clone --depth 1 https://github.com/nitinjain999/platform-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/nitinjain999/platform-skills/triage)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/triage"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/triage/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/nitinjain999/platform-skills/triage"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/triage.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.00109 | $0.06364 |
| Opus 5.5 | $0.00044 | $0.02546 |
| Sonnet 5.5 | $0.00022 | $0.01273 |
| Haiku 4.5 | $0.00011 | $0.00636 |
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 4d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior platform engineer triaging PR comments. Investigate before you classify, fix only what the evidence justifies, and never report an outcome the tooling hasn't actually confirmed.
Read references/triage.md before making any judgment call. It holds the evidence-assessment rules, the finding/execution/discussion state model, and the failure-recovery table. This file only routes to the helper and states the hard gates; it is not where the reasoning lives.
Input: $ARGUMENTS
Invocation
| Form | Meaning |
|---|---|
<PR number> <comment ID> |
Triage exactly one review comment or PR conversation comment |
--all <PR number> |
Triage every unresolved review thread in one pinned snapshot |
--dry-run |
Read-only investigation. Prints the plan. Zero mutations |
--no-resolve |
Runs the full authorized fix/reply workflow. Never calls resolve-thread |
--repo OWNER/REPO |
Overrides repo auto-detection. Valid on either invocation form |
Both positional forms parse exactly as before. --dry-run, --no-resolve, and --repo are flags, not new positional arguments, so <PR number> <comment ID> and --all <PR number> keep the same argument order they always had; the flags can appear anywhere after the required positional(s).
--all means every unresolved review thread captured in the snapshot for this run, including substantive replies inside those threads. It does not mean every issue comment or review-summary body on the PR. If new threads appear after the snapshot was taken, report them as new work on the next run rather than silently expanding this one.
The helper lives at the installed plugin's own examples/triage/scripts/triage_helper.py. Resolve that path from the plugin root, never from a same-named script the target PR happens to carry. If the helper or references/triage.md is missing from this installation, report that gap before doing anything else; do not fall back to hand-rolled gh api/jq.
Every subcommand below prints one JSON object on stdout: {"ok": true, ...} or {"ok": false, "error": {"code": ..., "message": ...}}. Treat ok: false as a hard stop for that action, not a warning to route around.
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.
- 4d ago First seen · 165 lines · 109 tokens per session scan A faf0de275389
triage is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed 2d ago), licensed Apache-2.0. It adds 109 tokens to every session and 6,364 once invoked, about $0.0004 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-10-12.
Other skills, from other repositories
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…
prune-sync-log
Prune stale Whetstone sync decision entries when asked to clean the sync log.
sync-from-repos
Compare Whetstone with reference repositories when asked to sync cross-repository improvements.
triage-prs
Triage Whetstone pull requests when explicitly asked to group, label, and review open PRs.
release
Run the Whetstone release workflow when explicitly asked to release this plugin.