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/issue-labelnpx skills add toss/es-toolkit --skill issue-labelgit clone --depth 1 https://github.com/toss/es-toolkitWhat 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.00013 | $0.00492 |
| Opus 5 | $0.00006 | $0.00246 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
issue-label 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 2d 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.
Issue Label
Analyze issue content and assign appropriate labels.
Input
$ARGUMENTS — Issue number (e.g. 1234)
Available Labels
| Label | When to use |
|---|---|
p0: major bug |
Core function broken, incorrect results, crashes |
p1: minor bug |
Edge case failures, non-critical behavior issues, type errors |
p1: docs bug |
Wrong/outdated documentation, broken links |
p2: optimization |
Performance improvements, bundle size reduction |
p2: new feature |
New function or capability request |
p2: type enhancement |
TypeScript type improvements, better generics |
p2: refactoring |
Code cleanup, internal improvements |
p2: docs enhancement |
New docs, translations, better examples |
p3: discussion |
Questions, design discussions, RFCs |
help wanted |
Good for external contributors |
Workflow
1. Fetch issue
gh issue view {number} --repo toss/es-toolkit --json title,body,labels
If labels already exist, report them and stop.
2. Analyze content
From title and body, identify:
- Is it a bug report? (error messages, "doesn't work", "incorrect", "doesn't match lodash")
- Is it a feature request? ("add", "implement", "support")
- Is it about docs? ("docs", "typo", "translation", "example")
- Is it about types? ("type", "TypeScript", "generic", "inference")
- Is it a question? (question marks, "how to", "is it possible")
3. Apply label
gh issue edit {number} --repo toss/es-toolkit --add-label "{label}"
4. Report
## Issue #{number} — {title}
### Applied Label: {label}
### Reason: {why this label fits}
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.
- 2d ago First seen · 65 lines · 13 tokens per session scan A 7063bed892a3
issue-label is a skill published in the GitHub repository toss/es-toolkit (11,320 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 492 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
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.