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 d-oit/rust-2026-template --skill issue-triagegit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/issue-triage)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/issue-triage"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/issue-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/d-oit/rust-2026-template/issue-triage"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.01979 |
| Opus 5.5 | $0.00041 | $0.00792 |
| Sonnet 5.5 | $0.00020 | $0.00396 |
| Haiku 4.5 | $0.00010 | $0.00198 |
Grade A, and why
issue-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 22d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage & Batch Implementation Skill
Overview
Workflow that orchestrates issue discovery → categorization → implementation planning → batch execution → CI verification → PR/MR merge.
Single PR/MR policy: All issues implemented in one PR/MR unless user specifies otherwise.
Exception: When issues have clear dependency layers (e.g., models → API → frontend), stacked PRs via gh stack may be used instead. See stacked-prs skill. Only when explicitly requested and repository is on GitHub.
Platform Detection
Auto-detect from git remote:
REMOTE=$(git remote get-url origin)
if echo "$REMOTE" | grep -qi "github"; then
PLATFORM="github"; CLI="gh"
elif echo "$REMOTE" | grep -qi "gitlab"; then
PLATFORM="gitlab"; CLI="glab"
else
echo "Unknown platform - set --platform github|gitlab"
fi
CLI Command Mapping
| Action | GitHub (gh) |
GitLab (glab) |
|---|---|---|
| List issues | gh issue list --state open |
glab issue list --state opened |
| Read issue | gh issue view 123 |
glab issue view 123 |
| Create PR/MR | gh pr create --title "..." |
glab mr create --title "..." |
| Check CI | gh pr checks |
glab ci status |
| Merge | gh pr merge 123 --squash |
glab mr merge 123 --squash |
| Close issue | gh issue close 123 |
glab issue close 123 |
Arguments
| Argument | Description | Default |
|---|---|---|
--repo OWNER/REPO |
Repository | auto-detect from git remote |
--platform github|gitlab |
Force platform | auto-detect |
--state open|closed|all |
Issue filter | open (GitHub) / opened (GitLab) |
--limit N |
Max issues to process | 50 |
--batch-size N |
Issues per PR/MR | all |
--dry-run |
Plan only, no implementation | false |
--skip-merge |
Create PR/MR but don't merge | false |
Prerequisites
ghCLI authenticated (gh auth status) — for GitHubglabCLI authenticated (glab auth status) — for GitLab- Repository hosted on GitHub or GitLab
- CI enabled (GitHub Actions / GitLab CI) for verification
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.
- 22d ago Changed · -5 lines bd483e491471
- 1mo ago First seen · 234 lines · 102 tokens per session scan A cbb454fcdb6b
issue-triage is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,979 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-08-31.
Other skills, from other repositories
publish-rust
Verify and release a Rust crate or workspace. Bumps version, commits, tags, pushes. CI-driven by default; --local publishes directly.
fix-issue
Fixes a bug, implements a missing feature, or implements one slice of a larger feature, starting from a GitHub issue link, number, or direct text description. Trigger when the user gives a GitHub issue URL/reference/description and asks to fix, implement, resolve, or work on it.
obsidian-mobile-sync
Setup Obsidian mobile sync via GitHub (free) or Obsidian Sync (paid). Includes GitHub CLI automation, MGit/Working Copy setup, and Mnemosyne integration patterns.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.