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 jeremylongworth-source/AgentSkills --skill issue-to-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/issue-to-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/issue-to-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/issue-to-plan/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/jeremylongworth-source/agentskills/issue-to-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/issue-to-plan.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.00052 | $0.00354 |
| Opus 5 | $0.00026 | $0.00177 |
| Sonnet 5 | $0.00010 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
issue-to-plan 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 7d 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.
What it actually says
Issue To Plan
Core Workflow
- Restate the requested behavior, current behavior, user impact, and success criteria.
- Identify missing reproduction details, environment, data, permissions, dependencies, and constraints.
- Inspect or request the relevant code, docs, logs, tickets, and tests before proposing risky changes.
- Break the work into small implementation steps with affected modules, interfaces, migrations, configuration, or documentation.
- Define acceptance criteria and verification before coding starts.
- Flag assumptions, sequencing risks, and decisions that need owner approval.
Safety Rules
- Do not claim a bug is fixed before implementation and validation.
- Do not recommend broad rewrites when a smaller change can satisfy the issue.
- Do not edit protected branches, merge, deploy, or close issues without explicit approval.
- Escalate when requirements conflict, reproduction is missing, security risk appears, or the change touches data, billing, auth, or production operations.
Deliverable Shape
For engineering plans, provide:
- Issue summary
- Known facts and missing information
- Affected areas
- Proposed implementation steps
- Acceptance criteria
- Test and verification plan
- Regression risks
- Open questions or approvals needed
References
- Read
references/issue-to-plan-checklist.mdwhen converting an issue, bug report, or feature request into an engineering plan.
What ships with it
2 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.
- 7d ago First seen · 48 lines · 52 tokens per session scan A adba19d3a022
issue-to-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 354 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
html-ppt-zhangzara-block-frame
Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
doca-dpa-hl-tracer
Use this skill when the user runs docadpahltracer to capture/decode DPA-side traces at the programming-events layer (kernel entry/exit, sync points, comm primitive calls, RDMA WR submission, completion drain) — picking TRACE vs CRIT, tuning the JSON config (file-size limits + filesizelimitpolicy, thread…
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime →…