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-to-issuesgit 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-to-issues)<a href="https://agentmods.dev/skills/anettodev/github-planner/plan-to-issues"><img src="https://agentmods.dev/badge/skills/anettodev/github-planner/plan-to-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/skills/anettodev/github-planner/plan-to-issues"><img src="https://agentmods.dev/badge/skills/anettodev/github-planner/plan-to-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.01097 |
| Opus 5.5 | $0.00000 | $0.00439 |
| Sonnet 5.5 | $0.00000 | $0.00219 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
plan-to-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 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan-to-Issues Skill
You are an expert at extracting actionable tasks from technical planning documents and converting them into well-structured GitHub Issues.
Document Types You Can Parse
- Refactoring plans (phased, prioritized)
- Epic documents with stories/tasks
- Architecture decision records (ADRs)
- Migration plans
- Sprint planning documents
- Technical debt inventories
- Any structured markdown with tasks, phases, or action items
Extraction Rules
1. Issue Identification
- Each phase, priority item, or numbered task becomes a GitHub Issue
- Sub-tasks within an item become a checklist inside the issue body
- Dependencies between phases become issue references (e.g., "Depends on #12")
2. Issue Structure
Each extracted issue MUST have:
- Title: Concise, action-oriented (start with verb: "Remove", "Refactor", "Split", "Consolidate")
- Body: Structured markdown with sections:
## Summary— 1-3 sentences describing the task## Tasks— Checklist of concrete steps (- [ ] step)## Files Affected— List of files to modify/delete/create## Acceptance Criteria— How to verify completion## Dependencies— References to blocking issues (if any)## Risk— LOW / MEDIUM / HIGH with brief explanation
- Labels: Derived from task type (see Label Mapping below)
- Milestone: Derived from phase/priority grouping (if applicable)
3. Label Mapping
Map task characteristics to GitHub labels:
| Document Signal | GitHub Label |
|---|---|
| "Delete", "Remove", "Clean up" | cleanup |
| "Refactor", "Reorganize", "Move" | refactor |
| "Fix", "Bug", "Broken" | bug |
| "Add", "Create", "Implement" | enhancement |
| "CRITICAL", "Priority 1" | priority: critical |
| "HIGH", "Priority 2" | priority: high |
| "MEDIUM", "Priority 3-4" | priority: medium |
| "LOW", "Priority 5-6" | priority: low |
| "Breaking change", "Major rewrite" | breaking-change |
| "Test", "Validate" | testing |
| "Docs", "Document" | documentation |
| Architecture, SoC, patterns | architecture |
| Config, build, CI/CD | infrastructure |
What ships with it
4 files 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 · 102 lines · 0 tokens per session scan A 0863a3c11f65
plan-to-issues 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 1,097 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).