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 skills add anettodev/github-planner --skill plan-insightsgit clone --depth 1 https://github.com/anettodev/github-plannerWrote 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/anettodev/github-planner/plan-insights)<a href="https://agentmods.dev/skills/anettodev/github-planner/plan-insights"><img src="https://agentmods.dev/badge/skills/anettodev/github-planner/plan-insights/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/anettodev/github-planner/plan-insights"><img src="https://agentmods.dev/badge/skills/anettodev/github-planner/plan-insights.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.00000 | $0.02786 |
| Opus 5.5 | $0.00000 | $0.01114 |
| Sonnet 5.5 | $0.00000 | $0.00557 |
| Haiku 4.5 | $0.00000 | $0.00279 |
Grade A, and why
plan-insights 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 2mo 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Insights Skill
You are an expert at analyzing project delivery metrics from GitHub data. You produce actionable reports on milestone progress, delivery pipeline health, and stale work — giving PMs the data they need to make sprint decisions.
Metrics
1. Milestone Burndown
Track progress toward each active milestone.
Data needed:
- Total issues in milestone (open + closed)
- Closed issues count and close dates
- Milestone due date (if set)
Calculations:
- Progress:
closed / total * 100 - Velocity: Issues closed per week over the last 4 weeks
- Projection: At current velocity, when will the milestone complete?
- Risk: If projected completion > due date → flag as AT RISK
Visualization:
Progress ████████░░░░░░░░░░░░ 36% 🟢 ON TRACK
Velocity ▂▄▅▇▅▃ 2.5/wk 🟡 DECLINING
- Progress bar: filled
█vs empty░, 20 chars wide - Sparkline:
▁▂▃▄▅▆▇█mapped to weekly closed counts (last 4-8 weeks) - Color dots: 🟢 on track / healthy, 🟡 at risk / declining, 🟠 stale, 🔴 behind / critical
Weekly breakdown:
| Week | Opened | Closed | Net | Remaining | Velocity |
|---|---|---|---|---|---|
| W12 | 14 | 0 | +14 | 14 | ▁ |
| W13 | 0 | 3 | -3 | 11 | ▃ |
| W14 | 1 | 5 | -4 | 8 | ▆ |
| W15 | 0 | 2 | -2 | 6 | ▃ |
Sparkline mapping: Scale the weekly closed count to 8 levels:
max_closed = max(weekly_closed_counts)- Each week:
level = round(closed / max_closed * 7)→ pick from▁▂▃▄▅▆▇█
Color status rules:
| Indicator | Condition |
|---|---|
| 🟢 ON TRACK | Progress % ≥ time elapsed % (or no due date and velocity stable) |
| 🟡 AT RISK | Progress % < time elapsed % by ≤ 15 points, or velocity declining 1 week |
| 🔴 BEHIND | Progress % < time elapsed % by > 15 points, or velocity declining 2+ weeks |
| 🟢 IMPROVING | Velocity increasing for 2+ weeks |
| 🟡 DECLINING | Velocity decreasing for 1 week |
| 🔴 STALLED | Zero issues closed for 2+ weeks |
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.
- 2mo ago First seen · 257 lines · 0 tokens per session scan A 2e5ff14c4416
plan-insights is a skill published in the GitHub repository anettodev/github-planner (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,786 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
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
gr-product-dev-ops
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified…
content-planner-auto
Use when auto-generate 30-day content calendars with pillar rotation, platform-optimized timing, multi-account rotation, seasonal Indonesian events, and PostBridge batch scheduling.
bugpack-list-bugs
List all tracked bugs from BugPack with status and project filtering. Use when: user asks about bugs, pending issues, bug lists, or wants to see what needs fixing. NOT for: viewing detailed bug context (use bugpack-view-bug) or fixing bugs (use bugpack-fix-bug).
planner-refine-assignments
Refine elaborated assignments for a single phase via parallel L0 subagents (L1+L0 pattern), using per-phase context file with peersummaries for cross-phase visibility.
planner-refine-wps
Refine elaborated work packages with cross-phase visibility via per-phase L0 subagents (L1+L0 pattern).