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 stefan-jansen/coding-agent-toolkit --skill next-issuegit clone --depth 1 https://github.com/stefan-jansen/coding-agent-toolkitWrote 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/stefan-jansen/coding-agent-toolkit/next-issue)<a href="https://agentmods.dev/skills/stefan-jansen/coding-agent-toolkit/next-issue"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/next-issue/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/stefan-jansen/coding-agent-toolkit/next-issue"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/next-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.02779 |
| Opus 5.5 | $0.00021 | $0.01112 |
| Sonnet 5.5 | $0.00011 | $0.00556 |
| Haiku 4.5 | $0.00005 | $0.00278 |
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 14d 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 — 263 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.
- 14d ago Changed · +43 lines 0a8ea775520b
- 1mo ago Changed · -30 tokens per session 8e87e28c2431
- 1mo 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 (33 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 2,779 once invoked, about $0.0002 per session on Opus 5.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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…