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 encoreshao/encore-skills --skill triage-issuegit clone --depth 1 https://github.com/encoreshao/encore-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/encoreshao/encore-skills/triage-issue)<a href="https://agentmods.dev/skills/encoreshao/encore-skills/triage-issue"><img src="https://agentmods.dev/badge/skills/encoreshao/encore-skills/triage-issue/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/encoreshao/encore-skills/triage-issue"><img src="https://agentmods.dev/badge/skills/encoreshao/encore-skills/triage-issue.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.00059 | $0.01395 |
| Opus 5 | $0.00030 | $0.00698 |
| Sonnet 5 | $0.00012 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
triage-issue 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Issue
Reads an issue and its comment thread, figures out which comments genuinely need a reply from you, grounds the reply in the actual codebase (not guesswork), drafts it in your own voice, and shows it to you — every time, no exceptions — before anything gets posted.
Input
- Issue number (
#42) with project alias or path, or a GitLab URL - A local clone of the relevant repo, if you want the reply grounded in current code (optional — skip Step 3 if there's no codebase)
GITLAB="$HOME/.claude/skills/gitlab-config/scripts/gitlab_api.py"
python $GITLAB whoami # confirm your username once per session
python $GITLAB sync-project <project> # once per project — builds the team/user directory
python $GITLAB sync-issue <project> <number> # issue + full comment thread, merged into the cache
See gitlab-config skill for first-time setup and the local-memory cache it maintains.
Steps
1. Fetch the issue and comments
Use sync-issue, not get-issue — same API call, but it merges onto whatever's already cached for this issue instead of discarding it, so any comment you've already handled (see Step 4) stays marked. It returns the issue plus every note in notes[], oldest-last. Each note has author, body, system (true = GitLab-generated, e.g. "assigned to @x" — never needs a reply), and created_at.
Resolve @mentions and author names against the cached team directory (gitlab_cache.py get-users <instance>) instead of guessing from the raw GitLab username — it's already built from sync-project and every issue you've synced.
2. Decide which comments need your reply
Walk the notes in chronological order (reverse the array first — GitLab returns newest-first). Skip system notes, anything you authored, and any note id already listed in the cached _notes.replied_note_ids (see Step 4 — you've handled it in a prior run). For everything else, a comment needs your reply if:
- It
@mentionsyour username directly, or - You're the assignee, it asks a direct question or requests an action, and no later comment from you addresses it
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.
- 11d ago First seen · 88 lines · 59 tokens per session scan A 5d04e79c9400
triage-issue is a skill published in the GitHub repository encoreshao/encore-skills (2 stars, last pushed 22d ago), licensed MIT. It adds 59 tokens to every session and 1,395 once invoked, about $0.0003 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
cron
Use this skill only for scheduled or recurring tasks. Manage jobs with qwenpaw cron list/create/get/state/pause/resume/delete/run, and always pass --agent-id explicitly.
cron
A scheduling tool for running tasks at a future time or repeating them on a set schedule. It manages scheduled jobs such as reminders, checks, and reports.
pm-init
Skill "pm-init" from wei63w/pm-manager, covering user input, outline, 1. scaffold, 2. lifecycle and type and 3. detect spec kit (required).
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
pm-arch
Skill "pm-arch" from wei63w/pm-manager, covering user input, outline, done when and shared workflow (all /pm- commands).
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).