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/anettodev/github-planner/issue-triagenpx skills add anettodev/github-planner --skill 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.02088 |
| Opus 5 | $0.00000 | $0.01044 |
| Sonnet 5 | $0.00000 | $0.00418 |
| Haiku 4.5 | $0.00000 | $0.00209 |
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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage Skill
You are an expert at analyzing GitHub issue backlogs from a product manager's perspective. You don't just organize — you evaluate what matters most for project health and user experience, and you give actionable recommendations.
Analysis Categories
1. Missing Labels
Flag issues that lack proper categorization:
- No labels at all → suggest type + priority
- Has type label but no priority → suggest priority
- Has priority but no type → suggest type
Use the same label taxonomy from plan-to-issues:
| Signal | Label |
|---|---|
| "Delete", "Remove", "Clean up" | cleanup |
| "Refactor", "Reorganize", "Move" | refactor |
| "Fix", "Bug", "Broken", "Crash" | bug |
| "Add", "Create", "Implement" | enhancement |
2. Priority Re-evaluation
Assess whether current priorities still make sense:
Escalation signals (suggest upgrading priority):
priority: lowor no priority + mentions "crash", "data loss", "security", "freeze" → suggestcriticalpriority: low+ labelbug+ affects core flow → suggesthigh- Blocks other issues (referenced as dependency) + no priority → suggest
high - Mentions "accessibility", "a11y" → suggest at least
medium
De-escalation signals (suggest downgrading or closing):
priority: high+ open 6+ months + no activity → suggest demoting tomediumor closingpriority: critical+ superseded by another issue → suggest closing as duplicate- Enhancement with no engagement (no comments, no reactions) after 90 days → suggest
lowor close
3. UX Impact Assessment
Flag issues that directly affect user experience. Score each issue:
High UX impact (keywords in title or body):
- "crash", "freeze", "ANR", "hang", "unresponsive"
- "can't login", "can't sign up", "can't access"
- "data loss", "lost data", "missing data"
- "broken UI", "layout broken", "display error"
- Touches: onboarding, authentication, navigation, checkout, core loops
Medium UX impact:
- "slow", "performance", "loading", "spinner"
- "confusing", "unclear", "hard to find"
- "accessibility", "a11y", "VoiceOver", "Dynamic Type"
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.
- 2d ago First seen · 219 lines · 0 tokens per session scan A 2c66e643d150
issue-triage is a skill 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 2,088 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 skills, from other repositories
backfill-enumerate-drain
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline. Load this when handling a .added seed event with the planner on.
summarize-assessment
Use after the napkinmath pipeline has produced parameters/bounds/scenarios/montecarlo JSON to generate a plan assessment (assessment.md) — a thin interpretation layer over the intermediary artifacts. Emits a JSON manifest, a provenance map, gate verdicts (Critical / Fragile / Marginal / Robust), failure drivers…
generate-bounds
Use when the user wants to generate low/base/high assumption ranges (bounds) for missing or uncertain variables in a validated extract-parameters-from-full JSON, in preparation for deterministic scenarios or Monte Carlo.
monte-carlo
Use when the user wants Monte Carlo simulation of a PlanExe model — sampling from bounds to produce output distributions (mean/std/percentiles), threshold pass probabilities, and Pearson-correlation sensitivity rankings — given an extract-parameters-from-full JSON, a generate-bounds JSON, a generate-calculations…
planexe-mcp
OpenClaw skill for connecting to PlanExe via Model Context Protocol. Supports three deployment scenarios: cloud-hosted service, remote Docker, and local Docker.
generate-calculations
Use when the user wants to turn a validated extract-parameters-from-full JSON into a Python module of deterministic functions implementing the formulahint expressions for downstream scenario runs and Monte Carlo.