Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/markerikson/opencode-config-examplenpx agentmods add skills/markerikson/opencode-config-example/issue-triage-toolWrote 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/markerikson/opencode-config-example/issue-triage-tool)<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/issue-triage-tool"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/issue-triage-tool/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/markerikson/opencode-config-example/issue-triage-tool"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/issue-triage-tool.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.00057 | $0.00900 |
| Opus 5.5 | $0.00023 | $0.00360 |
| Sonnet 5.5 | $0.00011 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
issue-triage-tool 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage Tool
Automates fetching, categorizing, and reporting on open GitHub issues/PRs for Redux ecosystem repos.
Prerequisites
- GitHub CLI (
gh) — must be installed and authenticated (gh auth login) - Bun — TypeScript runtime
Tool Location
The tool path is configured in ~/.config/opencode/scripts/config.json under toolPaths.issue-triage-tool.
Running the Tool
Basic Usage
# Triage RTK (most common)
bun src/index.ts --repo reduxjs/redux-toolkit
# Use cached data (skip API calls)
bun src/index.ts --repo reduxjs/redux-toolkit --use-cache
# Triage all repos
bun src/index.ts
Available Repos
| Repo | Flag Value |
|---|---|
| Redux Toolkit | --repo reduxjs/redux-toolkit |
| React Redux | --repo reduxjs/react-redux |
| Reselect | --repo reduxjs/reselect |
| Redux | --repo reduxjs/redux |
| Immer | --repo immerjs/immer |
CLI Flags
--repo <owner/name>— Process only this repository (default: all repos)--use-cache— Use cached data instead of fetching from GitHub API
Output
All output goes to cache/ directory within the tool folder.
| Path | Content |
|---|---|
cache/json/{owner}-{name}.json |
Raw issues + PRs JSON |
cache/issues-md/{owner}-{name}/*.md |
Individual issue markdown files |
cache/reports/{owner}-{name}/triage-report-full.md |
Full report: all categories, duplicates, clusters |
cache/reports/{owner}-{name}/triage-report-priority.md |
Shorter priority-focused report |
For RTK specifically:
cache/json/reduxjs-redux-toolkit.jsoncache/issues-md/reduxjs-redux-toolkit/cache/reports/reduxjs-redux-toolkit/triage-report-full.mdcache/reports/reduxjs-redux-toolkit/triage-report-priority.md
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.
- 1mo ago First seen · 121 lines · 57 tokens per session scan A 6b5cb9c58911
issue-triage-tool is a skill published in the GitHub repository markerikson/opencode-config-example (48 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 900 once invoked, about $0.0002 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-30.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…