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/mission69b/t2000/nextgit clone --depth 1 https://github.com/mission69b/t2000What 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.00012 | $0.00433 |
| Opus 5 | $0.00006 | $0.00217 |
| Sonnet 5 | $0.00002 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
next 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.
What it actually says
Figure out what to work on next.
Read these, in this order
audric/HANDOFF_NEXT_AGENT.md→ "Active backlog" table — this is the canonical, ranked list for product / agent-ownable tasks (with effort + notes) plus founder ops.HANDOFF_NEXT_AGENT.md(this repo) — the infra forward window and cross-repo cleanup. It defers the product backlog to the audric one, so don't treat a gap here as "nothing to do."PRODUCT.md— the product map SSOT (2 products: Private Inference · x402 gateway; one customer + one path each). Use it to sanity-check that a candidate task actually serves a live product rather than a retired surface.- Top of
audric-build-tracker.md— the last fewS.Nentries, to see what just landed and whether it left "founder ops owed" or "held for founder nod" items that are now unblocked.
All of these are local-only (gitignored, mounted from the private
mission69b/t2000-internal repo at spec/).
Then
Propose one next task. For it, state:
- What it is and which backlog row it came from.
- Why it's next (rank, or a dependency that just cleared).
- Rough effort.
- The verifiable acceptance criteria — what runnable check proves it's done.
- Which surfaces it touches (SDK / CLI / MCP / skills / docs — see
/ship).
Then run the product algorithm on it before writing any code: is the requirement actually sound, and is there a version of this task that deletes something instead of adding it? Say so if there is.
Do not start implementing until the user picks. List the runner-up briefly so they can redirect in one word.
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 · 41 lines · 12 tokens per session scan A fb87b5f0ef63
next is a command published in the GitHub repository mission69b/t2000 (23 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 433 once invoked, about $0.0001 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 commands, from other repositories
help
Show available commands for this app.
mesh
Show what the mesh can do right now — discover live capabilities and this agent's MESH balance.
handoff
Generate a comprehensive handoff document for transitioning a project between team members or to the client.
status
Generate a cross-project status report for all active client projects.
triage
Systematically triage open issues in the repository.
new-engagement
Set up a new consulting engagement with all required scaffolding.