plan-to-pr

plan-to-pr is a skill for Claude Code, Codex from jl-cmd/claude-dev-env. It costs 78 tokens per session (1,613 once invoked), scanned A, original, MIT.

A structured workflow for turning a software request into a pull request through a checked plan, separate implementation tasks, commits, review, and verification.

In plain words
What is it for?
Use it for planned feature work where each deliverable should have a defined file scope, acceptance check, verified commit, and independent review.
Why use it?
It keeps the work grounded in the repository's source and rules, while making each task, change, and acceptance check explicit. A failed plan validation stops implementation from starting.

Skill for Claude CodeCodex

Part of the claude-dev-env plugin — 64 skills, 3 commands, 9 agents, 8 hooks 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/jl-cmd/claude-dev-env/plan-to-pr
Any agent
npx skills add jl-cmd/claude-dev-env --skill plan-to-pr
Clone the repo
git clone --depth 1 https://github.com/jl-cmd/claude-dev-env

Made for: Claude Code, Codex.

Or install claude-dev-env, the plugin that ships this one along with the rest of its 64 skills, 3 commands, 9 agents, 8 hooks.

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-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/plan-to-pr.svg)](https://agentmods.dev/skills/jl-cmd/claude-dev-env/plan-to-pr)
Your own site
<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/plan-to-pr"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/plan-to-pr.svg" alt="Measured on agentmods" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,613 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.1 $0.00078 $0.01613
Opus 5 $0.00039 $0.00807
Sonnet 5 $0.00016 $0.00323
Haiku 4.5 $0.00008 $0.00161

Measured 5d ago against content hash 34109e393dd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

plan-to-pr 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 5d ago.

The scan reads SKILL.md. This mod also ships 13 executable files (scripts/config/__init__.py, scripts/config/constants.py, scripts/create_packet.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

packages/claude-dev-env/.agents/skills-archived/plan-to-pr/SKILL.md · 155 lines

How it starts

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

Plan-to-PR

Purpose and boundary

Use this skill for source-grounded implementation with one deliverable, one allowed file set, one acceptance check, and one commit per task. The planning phase creates and validates a tool-neutral docs/plans/<slug>/ packet before any TaskCreate or TodoWrite seeding.

The skill coordinates planning, task records, model routing, commit order, review, verification, and publication. It does not replace the orchestrator or advisor capabilities used by later phases.

Native planning phase

Run this phase before task seeding and before implementation:

  1. The Luna max planner reads the request, repository guidance, relevant source, tests, and documentation, then selects a unique lowercase slug.
  2. The planner consults a Sol xhigh advisor heavily at scope, dependency, task-boundary, acceptance, and risk decisions. The advisor supports planning decisions and packet review.
  3. The planner writes the packet files and validates them against reference/packet-contract.md and reference/packet-schema.json.
  4. The planner repairs packet findings and repeats deterministic validation until the packet passes. A failed validation blocks task seeding.
  5. Only a passing packet with status: approved may seed host tasks. Record the packet path and validation result in the task ledger.

The packet is the sole planning handoff. It contains its own scope, evidence, task boundaries, acceptance checks, risks, and implementation order. Do not seed tasks from conversational notes or an incomplete packet.

Capability boundary

This skill owns the native planning packet, task records, routing, review, verification, and publication decisions. Later execution uses the companion orchestrator and advisor capabilities.

Refusal cases

Refuse the first matching case and stop:

  • The request has no source-grounded plan packet.
  • The packet is missing, invalid, outside docs/plans/<slug>/, or not approved.
  • A requested change spans files outside the packet's allowed file set.
  • A task contains more than one deliverable, acceptance check, or commit.
  • A required task tool, verifier, model tier, advisor, review path, or gate is unavailable.
  • The user asks to bypass verification, review under the review guide, final validation, or a publication gate.

Read the full file on GitHub · 155 lines

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. 5d ago First seen · 155 lines · 78 tokens per session scan A 34109e393dd0

Subscribe to this mod's changes

plan-to-pr is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,613 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens