Borrowing it
Nothing to install: this file belongs to JeremyDev87/codingbuddy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JeremyDev87/codingbuddy/master/.claude/skills/plan-to-issues/SKILL.mdgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/plan-to-issues)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/plan-to-issues"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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/jeremydev87/codingbuddy/plan-to-issues"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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.00057 | $0.02698 |
| Opus 5.5 | $0.00023 | $0.01079 |
| Sonnet 5.5 | $0.00011 | $0.00540 |
| Haiku 4.5 | $0.00006 | $0.00270 |
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 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan to Issues
Convert a completed PLAN into GitHub parent + sub-issues using native sub-issue API.
Follow every step in order. Stop and report if any step fails.
Three Principles
- Independent — Each sub-issue is self-contained. A new session with zero context can start work from the issue alone.
- Deployable — Each sub-issue can be independently branched, PRed, and merged without breaking existing functionality.
- Structured — Issue body has essentials only. Technical details and background go into comments.
Step 1: Determine Plan Source
Check if $ARGUMENTS is provided:
-
With file (
/plan-to-issues docs/plans/my-plan.md): Verify the file exists (test -f "$ARGUMENTS"), then read it. Save the path:PLAN_FILE="$ARGUMENTS"(used later for bidirectional linking). -
With text (
/plan-to-issues "Add caching layer"): If$ARGUMENTSis not a valid file path, use it as plan description. SetPLAN_FILE=""(no file to link back to). -
Without arguments (
/plan-to-issues): Readdocs/codingbuddy/context.mdand extract the most recent PLAN section's decisions and notes. SetPLAN_FILE=""(no file to link back to).
If no plan source is found, stop and ask the user to run PLAN first.
Step 2: Check GitHub Environment
REPO=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
gh label list --json name --jq '.[].name'
Search for existing issues with similar titles to prevent duplicates:
gh issue list --state open --search "<plan-title-keywords>" --json number,title --jq '.[] | "#\(.number) \(.title)"'
If duplicates found, inform the user and ask whether to continue or update existing issues.
Step 3: Decompose into Deployable Units
Extract work units from the plan. For each candidate unit, verify:
For each unit:
Can this be merged independently without breaking existing features?
├── YES → Keep as separate sub-issue
└── NO → Merge with related unit(s) into one sub-issue
Does this modify the same files as another unit?
├── YES → Consider merging or enforce ordering
└── NO → Safe for parallel work
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 · 356 lines · 57 tokens per session scan A 06ec20c60839
plan-to-issues is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 2,698 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:planning-small-features
Planning the lightweight 4-gate Small Track pre-dev workflow (research, PRD, TRD, plan) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use…