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 Notysoty/openagentskills --skill issue-to-pr-plannergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/issue-to-pr-planner)<a href="https://agentmods.dev/skills/notysoty/openagentskills/issue-to-pr-planner"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/issue-to-pr-planner/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/notysoty/openagentskills/issue-to-pr-planner"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/issue-to-pr-planner.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.00027 | $0.01812 |
| Opus 5 | $0.00014 | $0.00906 |
| Sonnet 5 | $0.00005 | $0.00362 |
| Haiku 4.5 | $0.00003 | $0.00181 |
Grade A, and why
Issue to PR Planner 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 10d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue to PR Planner
What this skill does
This skill takes a GitHub issue (or any feature request / bug report) and turns it into a concrete, step-by-step implementation plan. It reads the codebase to identify the relevant files, understands the existing patterns, and produces an ordered list of changes with enough detail that a developer — or an agent executing the plan — can work through it without ambiguity.
Use this at the start of a feature or bug fix to align on exactly what needs to change before writing code, or to hand off implementation work to another developer or AI agent.
How to use
Claude Code / Cline
Copy this file to .agents/skills/issue-to-pr-planner/SKILL.md in your project root.
Then ask:
- "Use the Issue to PR Planner skill on this issue: [paste issue text]."
- "Plan the implementation for GitHub issue #142 using the Issue to PR Planner skill."
Provide the full issue text including the title, description, and any acceptance criteria or comments.
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Paste the issue text before asking for the plan.
Codex
Paste the issue text and provide the directory structure or key file list. Ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to plan an implementation from an issue, follow these steps:
Step 1 — Understand the issue
Read the issue thoroughly. Identify:
- Type: Bug fix, new feature, enhancement, refactoring, documentation
- Goal: What should be true after this is done?
- Acceptance criteria: Are there explicit criteria? If not, infer them from the description.
- Out of scope: What is the issue explicitly NOT asking for?
If the issue is ambiguous, note the ambiguity and state the assumption you're making to proceed.
Step 2 — Explore the codebase
Read the relevant parts of the codebase:
- Use the directory structure to find files related to the feature area
- Read the most relevant source files — entry points, the component or service mentioned in the issue, related tests
- Identify the existing patterns (naming conventions, how similar features are implemented, how tests are structured)
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.
- 10d ago First seen · 193 lines · 27 tokens per session scan A b5f8a586f765
Issue to PR Planner is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 26d ago), licensed MIT. It adds 27 tokens to every session and 1,812 once invoked, about $0.0001 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.
Other skills, from other repositories
github-cli
Automate GitHub workflows using the gh CLI for pull requests, issues, releases, actions, and repository management. Use when interacting with GitHub beyond basic git operations.
create-pr
This skill should be used when user asks to "create a PR", "make a pull request", "open PR for this branch", "submit changes as PR", "push and create PR", or explicitly invokes "create-pr".
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
lcx-contribute-bug-fix
Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the…