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 agents/h0x91b/dev-3.0/issue-trackergit clone --depth 1 https://github.com/h0x91b/dev-3.0What 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.00000 | $0.01000 |
| Opus 5 | $0.00000 | $0.00500 |
| Sonnet 5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
issue-tracker 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: dev-3.0 Kanban board
Issues and PRDs for this repo live as tasks on the dev-3.0 Kanban board, managed through the dev3 CLI (the same board this project ships). There is no separate issue tracker — a task is an issue. External GitHub PRs are pulled in as a secondary triage surface (see below).
Task and project are auto-detected from the worktree; pass --task <id> / --project <id> to target another.
Conventions (dev3 tasks)
- Create an issue:
dev3 task create --title "..." --description "..."— lands in the To Do (todo) column. For multiline Markdown, pipe it with--description -, for example:cat plan.md | dev3 task create --title "..." --description -. - Write long text:
task update --description -,note add --content -, andautomations ... --prompt -read the body from stdin;@fileremains the file-based alternative. - Read an issue:
dev3 task show --task <id> --notes --history(always prints the current overview;--notesinlines note bodies,--historyshows the title/overview change log). - List issues:
dev3 tasks list [--status <s>] [--label <id>] [--priority P0,P1] [--sort priority|seq] [--limit <n>] [--offset <n>]. Prints aPRIcolumn and orders each group the way the board orders a column — highest priority first, newest seq breaking ties;--sort seqrestores plain newest-first. Statuses:todo,in-progress,user-questions,review-by-ai,review-by-user. - Comment on an issue:
dev3 note add "..." --task <id>— per-task notes are the durable comment/scratchpad analog; they survive worktree teardown and are surfaced to future agents. - Apply / remove labels:
dev3 label set <id> [<id>...] --task <task>sets the task's labels to exactly the given ids (include every label the task should keep — it replaces the full set);dev3 label set --clear --task <id>removes all. Create a missing label first withdev3 label create "name" [--color "#hex"]; list withdev3 label list. - Set the overview (sticky summary):
dev3 overview set "..." --task <id>. - Change state / column:
dev3 task move --task <id> --status <status>. Note:completedandcancelledare UI-only, require user approval, and destroy the worktree — they are not a plain "close".
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 · 37 lines · 0 tokens per session scan A e53dc2747b71
issue-tracker is an agent published in the GitHub repository h0x91b/dev-3.0 (248 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,000 tokens. 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 agents, from other repositories
ap-feature-coordinator
L1 feature coordinator - drives approved ROADMAP.md lanes through their required build/review/verification gates and owns the run-wide feature frontier.
sweep-scan
You are a backlog sweeper. ./input.json names one repo and the exact source tree to read it against.
product-docs
Creates and updates process docs, templates, decision artifacts, and agent specs. TRIGGER when: (1) task adds or changes internal process documentation, (2) agent spec needs editing, (3) BACKLOG/TASKSTATUS templates need updating. SKIP: user-facing docs (use technical-writer), code changes.
technical-writer
Creates and updates user-facing project documentation. TRIGGER when: (1) task produces README, Getting Started guide, API reference, CHANGELOG, or tutorial, (2) external users need to understand the project. SKIP: internal process docs, BACKLOG/TASKSTATUS templates, code changes.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-framework-generator
L3 executor - FRAMEWORK GENERATE. When the SELECTOR returns MISS, generates a one-off custom framework for the exact task shape - classifies the orthogonal axes, composes the gate sequence from the GATE-LIBRARY with the correct axis-specific gate, emits the gen- leaf with the BLOCKED invariant verbatim, binds an…