plan-to-issue

plan-to-issue is a skill for Claude Code, Codex from dapi/claude-code-marketplace. It costs 279 tokens per session (968 once invoked), scanned A, original, MIT.

A workflow for saving an implementation plan as a GitHub issue, so another coding session can carry it out. GitHub issues are pages used to track tasks in a software repository.

In plain words
What is it for?
It helps find the latest plan file, gather the repository, branch, and folder details, and create a structured GitHub issue for implementation.
Why use it?
It keeps the plan and its repository context in one shared place instead of leaving instructions in a local file or chat. It also supports handing the work to a separate session.

Skill for Claude CodeCodex

Part of the github-workflow plugin — 3 skills, 1 command shipped together

Install

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.

agentmods
npx agentmods add skills/dapi/claude-code-marketplace/plan-to-issue
Any agent
npx skills add dapi/claude-code-marketplace --skill plan-to-issue
Clone the repo
git clone --depth 1 https://github.com/dapi/claude-code-marketplace

Made for: Claude Code, Codex.

Or install github-workflow, the plugin that ships this one along with the rest of its 3 skills, 1 command.

Wrote 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.

agentmods badge for plan-to-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/dapi/claude-code-marketplace/plan-to-issue.svg)](https://agentmods.dev/skills/dapi/claude-code-marketplace/plan-to-issue)
Your own site
<a href="https://agentmods.dev/skills/dapi/claude-code-marketplace/plan-to-issue"><img src="https://agentmods.dev/badge/skills/dapi/claude-code-marketplace/plan-to-issue.svg" alt="Measured on agentmods" height="20"></a>
Per session 279 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 968 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00279 $0.00968
Opus 5 $0.00139 $0.00484
Sonnet 5 $0.00056 $0.00194
Haiku 4.5 $0.00028 $0.00097

Measured 4d ago against content hash 2526d7cb3dfb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-to-issue 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 4d 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.

github-workflow/skills/plan-to-issue/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan to GitHub Issue

Save an implementation plan as a GitHub issue for execution in a separate Claude Code session.

Announce at start: "Saving implementation plan to GitHub issue."

Algorithm

Step 1: Find the plan file

Search from the git repository root:

REPO_ROOT=$(git rev-parse --show-toplevel)
ls -t "$REPO_ROOT"/docs/plans/*.md 2>/dev/null | head -1

If no plan files found, check if user specified a file path. If still nothing, report error: "No plan files found in docs/plans/. Please specify the plan file path."

Step 2: Read the plan

Read the plan file content using the Read tool.

Step 3: Gather context metadata

Run these commands to get repository and branch info:

# Repository (owner/repo format)
gh repo view --json nameWithOwner -q .nameWithOwner

# Current branch
git branch --show-current

# Working directory
pwd

Step 4: Compose the issue body

Structure the issue body as follows:

> **For Claude:** Use `superpowers:executing-plans` skill to implement this plan task-by-task.
> Start in the worktree directory shown below.

**Context**

| Field | Value |
|-------|-------|
| Repository | {owner/repo} |
| Branch | {branch-name} |
| Working directory | {pwd} |
| Plan file | {relative path to plan file} |

---

{Full plan file content}

Step 5: Extract title from plan

Parse the first # heading from the plan file as the issue title. If no heading found, use the filename (without date prefix and extension).

Step 6: Create the issue

Use --body-file - to handle large plans (avoids command-line length limits):

echo "$BODY" | gh issue create --title "{title}" --body-file - --label "plan"

If the "plan" label does not exist, create without labels:

echo "$BODY" | gh issue create --title "{title}" --body-file -

Step 7: Report result

Show the created issue URL and suggest how to use it:

"Plan saved to {issue_url}

To execute in a separate session:

  1. Open new Claude Code session in the worktree
  2. Tell Claude: 'Execute plan from {issue_url}'"

Read the full file on GitHub · 138 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 4d ago First seen · 138 lines · 279 tokens per session scan A 2526d7cb3dfb

Subscribe to this mod's changes

plan-to-issue is a skill published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 4mo ago), licensed MIT. It adds 279 tokens to every session and 968 once invoked, about $0.0014 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-30.

Related

Other skills, from other repositories

wayfinder

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

mattpocock/skills · 46 tokens

sap-transport-overview

System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…

arc-mcp/arc-1 · 106 tokens

timeline-creator

Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.

mhattingpete/claude-skills-marketplace · 47 tokens

pm-all

Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).

wei63w/pm-manager · 8 tokens

bootstrap-prd

Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.

joshukraine/dotfiles · 25 tokens

finn-spec

Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.

finna/Finn-loop · 56 tokens