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/nearform/lastlight/issue-triagenpx skills add nearform/lastlight --skill issue-triagegit clone --depth 1 https://github.com/nearform/lastlightWhat 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.00046 | $0.02032 |
| Opus 5 | $0.00023 | $0.01016 |
| Sonnet 5 | $0.00009 | $0.00406 |
| Haiku 4.5 | $0.00005 | $0.00203 |
Grade A, and why
issue-triage scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
closing, creating labels. Never `gh` CLI, `curl`, or raw HTTP. How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
Move each issue through a small state machine. Every triaged issue carries exactly one category role and one state role:
- Category:
bug(something is broken) ·enhancement(new feature or improvement) - State:
needs-triage(awaiting evaluation) ·needs-info(waiting on the reporter) ·ready-for-agent(fully specified, an AFK agent can take it) ·ready-for-human(needs human implementation) ·wontfix(won't be actioned)
These are canonical role names; the actual label strings for a repo may differ —
docs/agents/triage-labels.md holds the mapping when present. Run autonomously:
there is no maintainer to ask mid-run. Where you'd want direction, either make
the call and apply the label, or post a comment and stop — the async comment is
the conversation.
Your job is to classify the issue and pin down the problem statement — clarify what's actually being asked, and ask for missing information when it's under-specified. You do not design or plan the implementation: you have only read-only context and no deep exploration, so solution design is left to the downstream build agent, which has full source access.
0. Ensure the labels exist
Before applying any label, create the canonical set in a single idempotent
github_ensure_labels call — pass every row below as one labels array
({name, color}). It lists once and creates only the missing ones, so it never
errors on labels that already exist:
| Label | Color | Role |
|---|---|---|
bug |
d73a4a |
category |
enhancement |
a2eeef |
category |
needs-triage |
ededed |
state |
needs-info |
fbca04 |
state |
ready-for-agent |
0e8a16 |
state |
ready-for-human |
1d76db |
state |
wontfix |
ffffff |
state |
duplicate |
cfd3d7 |
dedupe |
question |
d876e3 |
question |
If the call is denied (the token lacks the permission), fall back to using only the labels that already exist on the repo and skip the rest. Done when the labels you need are present or you've confirmed you can't create them.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 168 lines · 46 tokens per session scan A 9ec096d4c15a
issue-triage is a skill published in the GitHub repository nearform/lastlight (22 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 2,032 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
b00t-gh-issues
GitHub issue triage and integration review agent for the b00ty-verse. Dogfoods b00t's grok RAG subsystem to research an issue topic, then posts a structured integration review on the GH issue. Evaluates external tools/frameworks/libraries for potential integration into the b00t ecosystem. Output is a machine-parseable…
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
github-issues
GitHub issue'larını gh veya REST ile oluştur, sırala, etiketle, ata.
gh-issue-triage
GitHub issue triage workflow with contributor profile extraction. Analyze → clarify → file cells → tag → implement → credit. Captures Twitter handles for changeset acknowledgments.
example-skill
Counts lines, words, and bytes in a text file using the bundled count.sh script. Use when asked to count/measure a file's size in these terms.
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.