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/mission69b/t2000Wrote 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/mission69b/t2000/tracker)<a href="https://agentmods.dev/commands/mission69b/t2000/tracker"><img src="https://agentmods.dev/badge/commands/mission69b/t2000/tracker/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/mission69b/t2000/tracker"><img src="https://agentmods.dev/badge/commands/mission69b/t2000/tracker.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.00018 | $0.00493 |
| Opus 5.5 | $0.00007 | $0.00197 |
| Sonnet 5.5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
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 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
Log the slice just shipped to audric-build-tracker.md: $ARGUMENTS
What this file is
A reverse-chronological execution log — one S.N entry per shipped slice,
newest at the top. It is the audit trail, NOT a forward backlog (that's
HANDOFF_NEXT_AGENT.md). It's gitignored here — the real file lives in the private
mission69b/t2000-internal repo, mounted at spec/.
Steps
- Read the top of
audric-build-tracker.mdto get the latestS.N. Increment it — never reuse or guess a number. - Confirm the work is actually shipped (committed / deployed), not just written.
- Insert the new entry immediately below the
**Rules:**block, above the current top entry.
Entry shape
Match the house style exactly — a heading, a one-line "why" with founder context where it exists, then bolded-lead bullets:
## S.<N> — <title> (<YYYY-MM-DD>)
<One or two lines: the driver / founder rationale / what forced this.>
- **<Category>:** what changed, concretely, with file or package names.
- **<Category>:** …
- **Founder ops owed (not in git):** anything requiring a human — DNS, Vercel
project deletion, npm deprecate, dashboard changes. Omit if none.
Categories used in practice: Deleted · Kept · Added · Git · Docs/config ·
Redirects · SSOT · Archive · Rules · Held for founder nod ·
Founder ops owed.
Rules
- Be specific. "Updated docs" is useless six months later; name the files.
- Record what was NOT done and why — held decisions, deferred pieces, ops owed.
- Don't editorialize the outcome. If something is partial or unverified, say so.
- One entry per slice. Don't retro-edit older entries to look tidier.
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 · 49 lines · 18 tokens per session scan A 5fdb3ed3af00
tracker is a command published in the GitHub repository mission69b/t2000 (23 stars, last pushed 26d ago), licensed MIT. It adds 18 tokens to every session and 493 once invoked, about $0.0001 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 commands, from other repositories
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.
triage
Systematically triage open issues in the repository.
new-engagement
Set up a new consulting engagement with all required scaffolding.
status
Generate a cross-project status report for all active client projects.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…