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.
git clone --depth 1 https://github.com/nkhdiscovery/headless-agentic-codebaseWrote 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/commands/nkhdiscovery/headless-agentic-codebase/next-issue)<a href="https://agentmods.dev/commands/nkhdiscovery/headless-agentic-codebase/next-issue"><img src="https://agentmods.dev/badge/commands/nkhdiscovery/headless-agentic-codebase/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/commands/nkhdiscovery/headless-agentic-codebase/next-issue"><img src="https://agentmods.dev/badge/commands/nkhdiscovery/headless-agentic-codebase/next-issue.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.00009 | $0.00232 |
| Opus 5.5 | $0.00004 | $0.00093 |
| Sonnet 5.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 1mo 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
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.
- 1mo ago 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 5mo ago), licensed MIT. It adds 9 tokens to every session and 232 once invoked, about $0.0000 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-31.
Other commands, from other repositories
release-update
(dev-only) release-update maintainer harness — Claude Code upstream change tracker (release-notes version-delta sweep + docs sync). NOT distributed to user projects.
github
(dev-only) github maintainer harness — GitHub issue-fix and PR-review via gh CLI. NOT distributed to user projects.
forge
Codev uses forge concept commands to interact with your repository hosting platform. By default, all concepts use the GitHub CLI (gh). Projects using GitLab, Gitea, or other forges can override these commands.
gate
Dispatch the moai workflow gate with: $ARGUMENTS.
team
The team command manages team members and messages for your Codev project. Team data is stored in codev/team/ and displayed in the Tower dashboard.
sync
Synchronize documentation, codemaps, and create pull request.