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/markerikson/opencode-config-example/issue-triage-toolnpx skills add markerikson/opencode-config-example --skill issue-triage-toolgit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWhat 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.00057 | $0.00900 |
| Opus 5 | $0.00028 | $0.00450 |
| Sonnet 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 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 — 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.
- 2d 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 (44 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 900 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.