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 agentmods add skills/feo2x/guided-coding/prepare-issue-for-plannpx skills add feO2x/guided-coding --skill prepare-issue-for-plangit clone --depth 1 https://github.com/feO2x/guided-codingWhat 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 | $0.00031 | $0.00612 |
| Opus 5 | $0.00015 | $0.00306 |
| Sonnet 5 | $0.00006 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
prepare-issue-for-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- guided-coding-prepare-issue-for-plan — 94% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare an Issue for a Plan
Create the issue and branch only. Leave planning to the user and the planning conversation.
1. Check prerequisites
Read the repository instructions. Before creating the issue:
- Run
git status. If the worktree has uncommitted changes, stop before creating the issue. - Determine the repository's default branch.
- Determine the issue tracker and target project from repository instructions. If they are not
documented, infer them only when the git remote and tracker clearly agree, such as
ghwith a GitHub remote. State the inferred target and ask the user to confirm it. - When a tracker exists, confirm that its CLI is available and authenticated for the target project. Check its help rather than guessing flags.
Use the title supplied by the user. If none is provided, ask for a short title. Derive a lowercase, hyphen-separated topic of at most four words.
Example: Support cancelled events becomes cancelled-events.
2. Update the default branch
Switch to the default branch and update it before creating the external issue:
git switch <default-branch>
git pull --ff-only
Stop if either command fails.
3. Create the issue
Create the issue with the agreed title and an empty description. Do not add a summary, acceptance criteria, or placeholder text. Use the tracker's documented CLI. For GitHub:
gh issue create --title "<title>" --body ""
Read the identifier and URL from the command output. Normalize the identifier for filenames and
branches: convert it to lowercase, remove a leading #, replace each run of characters other than
a-z and 0-9 with one hyphen, trim leading and trailing hyphens, and do not add zero padding. Stop
if normalization produces an empty identifier.
If the project has no issue tracker, skip issue creation and use the topic alone for the branch and later plan filename.
4. Create the branch
Create <issue-id>-<topic> or, without an issue, <topic>. Validate the complete name before
creating it:
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.
- 3d ago First seen · 75 lines · 31 tokens per session scan A 5015aa4600fa
prepare-issue-for-plan is a skill published in the GitHub repository feO2x/guided-coding (6 stars, last pushed 19d ago), licensed MIT. It adds 31 tokens to every session and 612 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…