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 agentmods add skills/toss/es-toolkit/pr-triagenpx skills add toss/es-toolkit --skill pr-triagegit clone --depth 1 https://github.com/toss/es-toolkitWrote 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/toss/es-toolkit/pr-triage)<a href="https://agentmods.dev/skills/toss/es-toolkit/pr-triage"><img src="https://agentmods.dev/badge/skills/toss/es-toolkit/pr-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 | $0.00014 | $0.00549 |
| Opus 5 | $0.00007 | $0.00275 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
pr-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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Triage
Classify and summarize a PR for review.
Input
$ARGUMENTS — PR number (e.g. 1234)
Workflow
1. Fetch PR info
gh pr view {number} --repo toss/es-toolkit --json title,body,author,files,labels
2. Classify the PR
Based on changed files, assign one or more labels:
| Pattern | Label | Review Focus |
|---|---|---|
src/compat/**/*.ts (not spec) |
compat-fix | Real lodash inconsistency? Use /compat-review to verify. |
src/{category}/*.ts (new file) |
new-function | Follows design principles? Checklist: impl + spec + re-export + docs. |
src/{category}/*.ts (modified) |
core-change | Intentional behavior change? Breaking changes? |
src/**/*.spec.ts |
test | Edge cases covered? |
docs/**/*.md |
docs | All 4 languages updated? Translation quality? |
Type-only changes in .ts |
types | Backward-compatible? |
benchmarks/** |
perf | Fair benchmark? Sound methodology? |
.github/**, config files |
infra | CI/build impact? |
3. Run quick checks per label
- compat-fix:
yarn vitest run src/compat/{category}/{fn}.spec.ts - new-function: Check all checklist items exist (impl, spec, re-export, 4 language docs)
- core-change:
yarn vitest run src/{category}/{fn}.spec.ts+tsc --noEmit - docs: Check all 4 language files present and consistent
- types:
tsc --noEmit
4. Report
## PR #{number} — {title}
### Classification: {labels}
### Changed Files
- {file list grouped by label}
### Quick Checks
- [ ] Tests pass
- [ ] Types pass
- [ ] {label-specific checks}
### Review Suggestions
{What to focus on based on the classification}
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 · 65 lines · 14 tokens per session scan A 096b550b1495
pr-triage is a skill published in the GitHub repository toss/es-toolkit (11,329 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 549 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…