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 commands/anettodev/github-planner/issue-triagegit clone --depth 1 https://github.com/anettodev/github-plannerWhat 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.00000 | $0.00974 |
| Opus 5 | $0.00000 | $0.00487 |
| Sonnet 5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00097 |
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 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Open Issues
Scan open issues, analyze backlog health, re-evaluate priorities, assess UX impact, and produce a PM-level triage report with actionable recommendations.
Arguments: $ARGUMENTS (optional flags: --repo owner/repo, --apply, --scope labels|priorities|stale|duplicates|epics|ux|all, --since 30d)
Steps
1. Detect Repository
- If
--repoflag provided, use that - Otherwise run
gh repo view --json nameWithOwner -q .nameWithOwner - Confirm: "Will analyze issues in
owner/repo."
2. Configure Scope
Parse flags:
--scope all(default): Run every analysis category--scope labels,priorities: Only run specified categories--since 30d: Only analyze issues updated in the last N days (useful for large backlogs)--apply: Enable interactive mode to apply suggested changes after review
Available scopes: labels, priorities, stale, duplicates, oversized, epics, ux, health, all
3. Run Analysis
Launch the issue-analyst agent to:
- Fetch all open issues and repository context (labels, milestones, projects)
- Analyze each issue across all selected categories
- Compute aggregate metrics (composition, age, assignment, coverage, UX health)
- Generate prioritized recommendations
4. Present Triage Report
Display the full report using the template from issue-triage skill's references/triage-report.md:
- Backlog Composition — bugs vs features vs refactoring vs unlabeled, with decision tips
- Issue Age Distribution — how old is the backlog, with decision tips
- Assignment & Ownership — who owns what, overloaded assignees
- Milestone & Epic Coverage — how many issues are planned vs orphaned
- UX Health Score — critical UX issues, impact assessment, score
- Findings — detailed tables for each category (missing labels, priority changes, stale, duplicates, oversized, epic suggestions, orphans)
- Recommended Actions — top 5-10 prioritized actions the PM should take
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 · 109 lines · 0 tokens per session scan A 689894b0545a
issue-triage is a command published in the GitHub repository anettodev/github-planner (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 974 tokens. 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 commands, from other repositories
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
task-hunter.skeleton
Kullanicinin girdisini asagidaki kurallara gore cozumle.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8 /task-conductor keyword auth -> /task-conductor plan keyword auth.
deadcode.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects Ornek cikti.
bug-review.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure Ornek cikti.
task-review.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure Ornek cikti.