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.
git 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/commands/anettodev/github-planner/plan-issues)<a href="https://agentmods.dev/commands/anettodev/github-planner/plan-issues"><img src="https://agentmods.dev/badge/commands/anettodev/github-planner/plan-issues/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/commands/anettodev/github-planner/plan-issues"><img src="https://agentmods.dev/badge/commands/anettodev/github-planner/plan-issues.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.00537 |
| Opus 5.5 | $0.00000 | $0.00215 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
plan-issues 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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issues from Planning Document
Parse a planning document and create GitHub Issues with labels, milestones, and dependency tracking.
Arguments: $ARGUMENTS (required — path to planning document, optional flags: --repo owner/repo, --dry-run)
Steps
1. Load Document
- Read the file at the provided path
- Detect document type: refactoring plan, migration plan, epic, tech debt inventory, or generic task list
- If
--dry-runis specified, switch to preview mode (same as/plan-preview)
2. Detect Repository
- If
--repoflag provided, use that - Otherwise run
gh repo view --json nameWithOwner -q .nameWithOwner - Confirm with user before proceeding: "Will create issues in
owner/repo. Continue?"
3. Extract Tasks
Use the plan-to-issues skill to parse the document:
- Identify each phase, priority item, or numbered task → becomes an issue
- Identify sub-steps → become checklists within the issue body
- Map task signals to labels (see skill for label mapping table)
- Group by phase/priority → milestones
- Track dependencies between items
4. Check for Existing Issues
For each extracted task, search for potential duplicates:
gh issue list --search "KEY_WORDS" --state open --limit 5 --json number,title
If duplicates found, skip those tasks and report them.
5. Present Plan for Approval
Show the full plan before creating anything:
Will create N issues in owner/repo:
| # | Title | Labels | Milestone |
|---|--------------------------------|----------------------------|---------------|
| 1 | Remove dead files | cleanup, priority: critical | Phase 1 |
| 2 | Consolidate duplicates | refactor, priority: high | Phase 1 |
...
New labels to create: priority: critical, cleanup, ...
New milestones to create: Phase 1, Phase 2, ...
Proceed? (yes/no)
DO NOT create issues until user confirms.
6. Create Labels and Milestones
Create any missing labels and milestones before creating issues.
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.
- 1mo ago First seen · 75 lines · 0 tokens per session scan A 69573d0d8fb3
plan-issues is a command published in the GitHub repository anettodev/github-planner (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 537 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
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.