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/florianbruniaux/claude-code-plugins/issue-triagenpx skills add FlorianBruniaux/claude-code-plugins --skill issue-triagegit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/issue-triage)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/issue-triage"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/issue-triage.svg" alt="Measured on agentmods" 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 | $0.00081 | $0.03848 |
| Opus 5 | $0.00041 | $0.01924 |
| Sonnet 5 | $0.00016 | $0.00770 |
| Haiku 4.5 | $0.00008 | $0.00385 |
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.
- Use `gh` CLI (not `curl` GitHub API) except for collaborators list How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
3-phase workflow for maintainers: automated audit of all open issues, opt-in deep analysis via parallel agents, and validated triage actions (comments, labels, closures).
When to Use This Skill
| Skill | Usage | Output |
|---|---|---|
/issue-triage |
Sort, analyze, and act on an issue backlog | Triage tables + analysis + executed actions |
/pr-triage |
Sort, review, and comment on a PR backlog | Triage table + reviews + posted comments |
Triggers:
- Manually:
/issue-triageor/issue-triage allor/issue-triage 42 57 - Proactively: when >10 open issues without label, or stale issues >30 days detected
Language
- Check the argument passed to the skill
- If
enorenglish→ tables and summary in English - If
fr,french, or no argument → French (default) - Note: GitHub comments and labels (Phase 3) are ALWAYS in English (international audience)
Configuration
Thresholds used throughout the workflow. Edit to match your project:
| Parameter | Default | Description |
|---|---|---|
staleness_days |
30 | Days without activity before flagging as stale |
very_stale_days |
90 | Days without activity before flagging as very stale |
jaccard_threshold |
60% | Minimum Jaccard similarity to flag two issues as duplicates |
closed_compare_count |
20 | Number of recent closed issues to compare for duplicate detection |
open_limit |
100 | Maximum open issues to fetch and analyze |
Preconditions
git rev-parse --is-inside-work-tree
gh auth status
If either fails, stop and explain what is missing.
Phase 1: Audit (always executed)
Data Gathering (parallel commands)
# Repo identity
gh repo view --json nameWithOwner -q .nameWithOwner
# Open issues (exclude PRs, limit 100)
gh issue list --state open --limit 100 \
--json number,title,author,createdAt,updatedAt,labels,body,comments,assignees,milestone
# Recent closed issues (for duplicate detection)
gh issue list --state closed --limit 20 \
--json number,title,body,labels,stateReason
# Open PRs (bodies for cross-reference detection)
gh pr list --state open --limit 50 --json number,title,body
# Collaborators (to distinguish reporter types)
gh api "repos/{owner}/{repo}/collaborators" --jq '.[].login'
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 · 449 lines · 81 tokens per session scan A 446862ff065a
issue-triage is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 3,848 once invoked, about $0.0004 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-09-04.
Other skills, from other repositories
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
doctor
OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned…
setup
创建一个新的 Workframe 项目，或把已有项目接入 Workframe。按用户意图与目标目录状态分流（新建 / 接入），对话采集业务上下文后落骨架、订阅 core 插件、完成落盘验收。仅用于 Workframe 框架的项目初始化，不承担 npm init / create-react-app / git init 等通用脚手架。.
code-review
代码审查，从需求符合度/正确性/安全性/可维护性/性能五维度评审代码变更，输出风险分级的 Finding 列表.
technical-design
技术方案设计与实施，提供轻量路径（小改动直接落地）和完整路径（架构/数据/API/多文件高风险变更走完整方案+实施+交付）双档分流.
audit
审计最近一段时间的自动维护活动（events / proposals / decay / digest），给用户汇总报告.