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 commands/nkhdiscovery/headless-agentic-codebase/next-issuegit clone --depth 1 https://github.com/nkhdiscovery/headless-agentic-codebaseWhat 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.00009 | $0.00232 |
| Opus 5 | $0.00005 | $0.00116 |
| Sonnet 5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
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 yesterday.
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
Identify and start the next issue.
gh issue list --label ready-for-agent --state open --json number,title,labels --limit 20- Priority order:
priority:highfirstpriority:mednextpriority:lownext- Unlabelled priority last
- Tie-break by issue number (lowest first).
- Skip issues also labelled
blocked,needs-decision,human-only,in-progress. - Skip issues labelled
trackingorroadmap— these are epics, decompose them instead. - Print chosen issue number, title, body.
- Add
in-progresslabel:gh issue edit <N> --add-label in-progress - Comment on issue: "Starting work. Branch: agent/-."
- Append "IN PROGRESS" entry to
logs/progress.md.
If no eligible issues, say so and stop — the work loop will run self-audit instead.
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.
- yesterday First seen · 22 lines · 9 tokens per session scan A d7a65be9fabb
next-issue is a command published in the GitHub repository nkhdiscovery/headless-agentic-codebase (10 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 232 once invoked, about $0.0000 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 commands, from other repositories
implement
Execute phased implementation with validation gates.
workflow-claude-commands
Track Claude Code commands report changes and find what needs updating.
workflow-claude-subagents
Track Claude Code subagents report changes and find what needs updating.
weather-orchestrator
Fetch Dubai weather and create an SVG weather card.
agent-farm
The afx (agent-farm) command manages multi-agent orchestration for software development. It spawns and manages builders in isolated git worktrees.
oss-docs
(user-owned) oss-docs harness — README 4-locale + docs-site publishing for the moai-adk-go OSS project (adk.mo.ai.kr, Vercel auto-deploy).