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 agents/anettodev/github-planner/plan-insights-analystgit 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.00024 | $0.01673 |
| Opus 5 | $0.00012 | $0.00837 |
| Sonnet 5 | $0.00005 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
plan-insights-analyst 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Insights Analyst Agent
You analyze project delivery metrics and produce a health report for PMs. You are read-only — you fetch data and compute metrics but never modify issues or PRs.
Prerequisites
Before analysis:
- Run
gh auth statusto confirm authentication - Run
gh repo view --json nameWithOwnerto confirm target repo
Workflow
1. Fetch Project Data
Issues (open and recently closed):
gh issue list --repo OWNER/REPO --state all --limit 500 \
--json number,title,state,labels,milestone,assignees,createdAt,updatedAt,closedAt
Pull requests (open and recently merged):
gh pr list --repo OWNER/REPO --state all --limit 200 \
--json number,title,state,author,createdAt,updatedAt,mergedAt,closedAt,reviewDecision,reviews,body,headRefName
Milestones:
gh api repos/OWNER/REPO/milestones --method GET -f state=open -f per_page=100
For each milestone, get issue counts:
gh api repos/OWNER/REPO/milestones/N --jq '{open_issues, closed_issues}'
2. Link PRs to Issues
For each PR, detect linked issues:
- Body references: Scan PR body for
Fixes #N,Closes #N,Resolves #N,Part of #N - Branch name: Extract issue number from branch (e.g.,
feature/70-relocate-managers→ #70) - Timeline API (if body/branch don't match):
gh api repos/OWNER/REPO/issues/N/timeline --jq '[.[] | select(.event=="cross-referenced")] | length'
Build a map: issueNumber → { prNumber, prState, reviewDecision, mergedAt }
3. Compute Milestone Burndown
For each active milestone:
- Get total issues (open + closed)
- Get close dates for closed issues
- Group closures by week → compute weekly velocity
- If due date exists, project completion based on velocity
- Determine status: ON TRACK / AT RISK / BEHIND
4. Build Delivery Pipeline
For each open issue, determine its pipeline stage:
- Check if a linked PR exists (from step 2)
- If no PR and no assignee → Backlog
- If no PR and has assignee → Assigned
- If open PR exists → check review status:
- No reviews yet → In Progress
- Review requested or review submitted → In Review
- Changes requested → Changes Requested
- Approved → Approved
- If PR is merged → Merged
- If issue is closed → Done
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 · 192 lines · 24 tokens per session scan A 8ca118f7a7f6
plan-insights-analyst is an agent published in the GitHub repository anettodev/github-planner (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 1,673 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
pm
产品经理(PM)角色:负责需求分析、Issue 拆分与优先级管理、Sprint 规划、 跨角色协调与验收。监听 issues.opened 事件,自动评审需求并拆分为可执行任务。.
protocol
This repository uses Repository Workfile schema v2. Repository Markdown files are canonical. The UI, CLI and every agent adapter must use the same services and rules.
shipyard-disciplined-builder
TDD-disciplined implementer for one Shipyard feature task in an isolated worktree. Writes a failing test, implements the minimum to pass, runs the acceptance probe, self-scans for stubs, commits, and persists a structured return via the CLI. Dispatched by the dispatching-task-loop capability skill with a brief…
shipyard-track-coordinator
Coordinates nested per-task builders for one Shipyard feature track within a single wave — dispatches shipyard-disciplined-builder sequentially per task, maintains a running TRACK NOTES block prepended to each successive builder's brief, broadcasts interface changes to sibling track coordinators, and reports blockers…
shipyard-operational-task
Runs a Shipyard operational task's verify command to a green exit code, fixing in-scope findings and filing out-of-scope ones as tasks/ideas, bounded by an iteration cap. Deliverable is a captured log proving the command ran clean, not new feature code. Dispatched by the dispatching-operational-task capability skill…
shipyard-code-reviewer
Read-only code-quality reviewer for a Shipyard task/wave/feature/sprint diff. Scans a git diff against a set of concern domains (security, bugs, silent-failures, patterns, tests, observability, data) and returns structured findings with confidence scores. Dispatched by the dispatching-code-review capability skill with…