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/wasintoh/toh-framework/toh-shipgit clone --depth 1 https://github.com/wasintoh/toh-frameworkWrote 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/wasintoh/toh-framework/toh-ship)<a href="https://agentmods.dev/commands/wasintoh/toh-framework/toh-ship"><img src="https://agentmods.dev/badge/commands/wasintoh/toh-framework/toh-ship.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00983 |
| Opus 5 | $0.00008 | $0.00491 |
| Sonnet 5 | $0.00003 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
toh-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 5d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/toh-ship - Deploy to Production
Signature Command 🚀
/toh-ship [platform]
/toh-s [platform]
What Happens
0. 🚨 READ MEMORY (Tiered Loading — don't blind-read all 7)
├── Tier 1 · ALWAYS at start (~800 tokens)
│ ├── .toh/memory/active.md (current task)
│ └── .toh/memory/summary.md (project overview)
├── Tier 2 · read per task type
│ ├── .toh/memory/architecture.md (structure — build/code work)
│ ├── .toh/memory/components.md (existing components — build/code work)
│ └── .toh/memory/changelog.md (recent changes — debug/release notes)
└── Tier 3 · read ONLY when referenced
├── .toh/memory/decisions.md (past decisions)
└── .toh/memory/agents-log.md (agent activity)
1. PRE-FLIGHT Checks
├── npm run build (must pass)
├── npm run lint (should pass)
├── Check environment variables
└── Verify .gitignore
2. PREPARE
├── Update next.config.js if needed
├── Create/update vercel.json
└── Check for hardcoded localhost URLs
3. DEPLOY
├── Vercel: npx vercel --prod
├── Netlify: netlify deploy --prod
└── Others: provide instructions
4. POST-DEPLOY
├── Verify live site works
├── Check environment variables are set
└── Test critical flows
5. 🚨 SAVE MEMORY
├── Update active.md (ALWAYS — deployed URL)
├── Update summary.md (production URL — project shape changed)
├── Update changelog.md (deployment)
├── Update decisions.md (deployment config)
└── Update agents-log.md (if agents delegated)
Example Prompts
# Default (Vercel)
/toh-ship
# Specific platform
/toh-s vercel
/toh-ship netlify
# With checks
/toh-s deploy with full checks first
Output Format
## 🚀 Deployed successfully!
### Pre-flight:
- ✅ Build passed
- ✅ No TypeScript errors
- ✅ Environment variables ready
### Deployed to:
**https://your-app.vercel.app**
### Environment Variables to set in Vercel:
NEXT_PUBLIC_SUPABASE_URL=xxx NEXT_PUBLIC_SUPABASE_ANON_KEY=xxx NEXT_PUBLIC_LIFF_ID=xxx (if using LINE)
### Closing:
Close per **engineer-harness Section C** (announce block: Status / Result / Evidence + exactly 3 next actions). Default trio for the shipped stage:
1. `/toh-test` — regression safety net ← recommended
2. `/toh-plan <new feature>` — next feature
3. business-type fit (F&B → payments, receipts · E-commerce → Stripe, order emails · Booking → calendar sync · SaaS → user roles, billing)
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.
- 5d ago First seen · 131 lines · 15 tokens per session scan A 2e18e9ab0b2b
toh-ship is a command published in the GitHub repository wasintoh/toh-framework (95 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 983 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
brainstorm
Command dispatcher for brainstorm.
planflow
Draft a plan and get it approved as an editable flowchart in the browser before executing.
stop
Deactivate Agentic Loop for this conversation and safely checkpoint unfinished work.
workflow-create
Command "workflow-create" from smith-horn/skillsmith, covering workflow-create, usage, options, examples and author deploy-api.yaml, then register it as a template.
workflow-execute
Command "workflow-execute" from smith-horn/skillsmith, covering workflow-execute, usage, options, examples and dry run (old: --name "deploy-api" --dry-run).
hello
Trivial hello command from example. Used to verify plugin installation works end-to-end.