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/ship)<a href="https://agentmods.dev/commands/mission69b/t2000/ship"><img src="https://agentmods.dev/badge/commands/mission69b/t2000/ship/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/ship"><img src="https://agentmods.dev/badge/commands/mission69b/t2000/ship.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.00020 | $0.00874 |
| Opus 5.5 | $0.00008 | $0.00350 |
| Sonnet 5.5 | $0.00004 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
ship 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 27d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the ship checklist for: $ARGUMENTS
Work through each item. For each, either do it, or state explicitly why it doesn't apply to this slice. Don't silently skip.
Surfaces
- SDK implementation + tests (
packages/sdk/src/) - CLI command + tests (
packages/cli/src/commands/) - MCP tool + tests (Connect —
audric/apps/mcp/lib/tools.ts) - Agent Skill (
t2000-skills/skills/) — only on lifecycle/policy/money-rule changes; never for Connect card/nextpolish (tools/list is the inventory SSOT) - Mintlify docs (
apps/docs/*.mdx) — auto-deploys to docs.t2000.ai - Root
README.md - Package
README.mds - Machine front door — if this slice changed a machine contract
(public
api.t2000.ai/v1/*paths/shapes agents rely on · CLI marketplace/wallet verbs agents are told to run · Connect auth model or connector URL · discovery URLs · who can sign · earn-first/fee/ open-reject locks), updateaudric/apps/console/app/llms.txt/route.tsand confirm every URL it cites returns non-5xx. UI polish/copy nits don't fire the gate — write N/A. Depth:.claude/skills/t2000-machine-front-door/SKILL.md - Version bump + build all packages (
/release)
Tests live inline next to source (Foo.ts + Foo.test.ts) — never add a new
__tests__/ folder.
Docs cadence — two tiers, not "dump as you go"
- Per-slice (now): keep docs.t2000.ai factually correct only — version, command surface, behavior (limits-on, no-charge-on-failure). Cheap; prevents the staleness class.
- Per-phase (later): a dedicated structured-docs task turning the phase's specs into a story-driven product + technical section (features → benefits → how it works), not a textbook manual.
Catalog tables come from live truth, never from memory
Any docs table enumerating services / models / tools / skills MUST be written against the live source:
- Store Services →
api.t2000.ai/v1/services - Model catalog →
api.t2000.ai/v1/models - MCP tools →
audric/apps/mcp/lib/tools.ts(Connect; stdio package is deprecated/frozen) - Skills →
t2000-skills/skills/ - CLI defaults → the CLI source
- Passport plan SKUs / prices / featured caps →
audric/packages/accounts/src/tiers.ts+featured-cap.ts
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.
- 27d ago Changed · +7 lines f3e8053a58ff
- 1mo ago First seen · 65 lines · 20 tokens per session scan A c9a0126c8ca2
ship is a command published in the GitHub repository mission69b/t2000 (23 stars, last pushed 26d ago), licensed MIT. It adds 20 tokens to every session and 874 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
changelog
Generate a changelog from git commits since the last release tag.
release
Prepare and publish a semver-compliant release.
ship
Pre-ship checklist and deployment. Run this before every production deploy.
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.