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/plan-insightsgit 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.00555 |
| Opus 5 | $0.00000 | $0.00278 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
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 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Delivery Insights
Analyze project delivery metrics — milestone burndown, delivery pipeline, stale work, and overall project health.
Arguments: $ARGUMENTS (optional flags: --repo owner/repo, --scope burndown|pipeline|stale|health|all, --milestone "name", --period 30d)
Steps
1. Detect Repository
- If
--repoflag provided, use that - Otherwise run
gh repo view --json nameWithOwner -q .nameWithOwner
2. Configure Scope
Parse flags:
--scope all(default): Generate full report--scope burndown: Milestone burndown only--scope pipeline: Delivery pipeline only--scope stale: Stale work detection only--scope timeline: ASCII Gantt timeline only--scope ci: CI/CD health only--scope health: Summary dashboard only--milestone "name": Filter to a specific milestone--period 30d(default): Time window for velocity and activity metrics
3. Run Analysis
Launch the plan-insights-analyst agent to:
- Fetch all issues, PRs, and milestones
- Link PRs to issues (body references, branch names)
- Compute milestone burndown with velocity projections
- Build the delivery pipeline (backlog → assigned → in progress → review → merged → done)
- Detect stale work using the configured threshold (
__STALE_THRESHOLD__days, default 14) - Compute PR metrics (review turnaround, time to merge, PR size)
- Build the health summary dashboard
- Generate prioritized recommendations
4. Present Report
Display the full report using the template from plan-insights skill's references/plan-insights-report.md:
- Milestone Burndown — progress, velocity, projection, weekly breakdown
- Delivery Pipeline — issues by stage, bottleneck detection
- Stale Work — idle issues, PRs, and reviews by severity
- Timeline — ASCII Gantt with milestones, progress bars, and critical path
- CI/CD Health — workflow success rates, blocked PRs, flaky tests, deploy frequency
- Project Health Summary — aggregate metrics with status indicators
- Recommended Actions — prioritized list of what to do next
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 · 54 lines · 0 tokens per session scan A 442864f5ec34
plan-insights 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 555 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.
pre-deploy.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects Ornek cikti.
review-module.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects Ornek cikti.