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/stefan-jansen/coding-agent-toolkit/next-issuenpx skills add stefan-jansen/coding-agent-toolkit --skill next-issuegit clone --depth 1 https://github.com/stefan-jansen/coding-agent-toolkitWhat 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.00083 | $0.02237 |
| Opus 5 | $0.00042 | $0.01118 |
| Sonnet 5 | $0.00017 | $0.00447 |
| Haiku 4.5 | $0.00008 | $0.00224 |
Grade A, and why
next-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 2d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
next-issue — implement the next open issue in the milestone
You are running the NEXT-ISSUE step of the workflow. Your job is to take ONE open GitHub issue (the next in line for the active milestone) and ship the implementation as commits on a feature branch, so that the PR for the milestone moves forward by exactly one issue.
This step is host-neutral: same contract on Claude and Codex. The verbs are
gh, git, and whatever the project's test runner is (uv run pytest, npm test, etc.).
Arguments
Parse these from the user's invocation (any order):
| Arg | Required | Default | Meaning |
|---|---|---|---|
--repo <owner/name> |
no | current repo via gh repo view --json nameWithOwner |
Target GitHub repo |
--milestone <title> |
no | the most recently active milestone with open issues | Restrict picking to this milestone |
--issue <N> |
no | lowest-numbered open issue in milestone | Explicitly target one |
--branch <name> |
no | reuse current branch if it matches the milestone's PR; otherwise feat/<milestone-slug> |
Feature branch name |
--dry-run |
no | false (act) | Print what would happen, change nothing |
Default behavior is to act, not dry-run — implementing code is the point of
the verb. --dry-run is for "show me what's next" without starting work.
Unlike /plan-issues, next-issue mutates the working tree by design. Use
--dry-run to preview the pick without touching code.
What "active milestone" means
If --milestone is not given, resolve it like this:
- List open milestones in the repo:
gh api "repos/<owner>/<repo>/milestones?state=open" --jq '.[].title' - If exactly one is open → pick it.
- If multiple → ask the user, listing them with their open-issue count from
gh issue list --milestone "<title>" --state open --json number. - If zero → tell the user there's nothing to pick up and stop. Suggest
/plan-issuesor a new milestone.
What "next issue" means
Lowest-numbered open issue in the chosen milestone:
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.
- 2d ago First seen · 220 lines · 83 tokens per session scan A 20dac53b277a
next-issue is a skill published in the GitHub repository stefan-jansen/coding-agent-toolkit (22 stars, last pushed 16d ago), licensed MIT. It adds 83 tokens to every session and 2,237 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-30.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.