toh-dev

A development command for adding application behavior behind an existing interface. It covers logic, stored application state, TypeScript type definitions, and create-read-update-delete (CRUD) operations.

In plain words
What is it for?
Use it to add data flows, state management, typed code, forms, and CRUD features such as creating, viewing, editing, and deleting records.
Why use it?
It turns screens into working features by organizing the data and actions they need, while checking for common security problems before coding.

Command

Install

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.

agentmods
npx agentmods add commands/wasintoh/toh-framework/toh-dev
Clone the repo
git clone --depth 1 https://github.com/wasintoh/toh-framework
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,074 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01074
Opus 5 $0.00006 $0.00537
Sonnet 5 $0.00003 $0.00215
Haiku 4.5 $0.00001 $0.00107

Measured 2d ago against content hash 1572d05a05ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

toh-dev 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.

src/commands/toh-dev.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/toh-dev - Add Logic & State

Signature Command ⚙️

/toh-dev [description]
/toh-d [description]

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 work)
   └── Tier 3 · read ONLY when referenced
       ├── .toh/memory/decisions.md    (past decisions)
       └── .toh/memory/agents-log.md   (agent activity)

1. READ Skills
   ├── ~/.toh/skills/dev-engineer/SKILL.md
   └── ~/.toh/skills/security-engineer/SKILL.md

2. 🔐 QUICK SECURITY CHECK (before coding)
   ├── Scan for hardcoded secrets
   ├── Check for dangerous patterns
   └── If CRITICAL found → WARN before proceeding

3. ANALYZE Request
   ├── Need types? → Create in types/
   ├── Need state? → Create Zustand store in stores/
   ├── Need forms? → Add React Hook Form + Zod
   └── Need CRUD? → Create in lib/api/

4. IMPLEMENT
   ├── TypeScript types (strict, no any)
   ├── Zustand store with actions
   ├── Zod validation schemas
   ├── Mock CRUD operations
   └── Custom hooks if needed

5. CONNECT to UI
   └── Wire up components to stores/forms

6. 🔐 POST-IMPLEMENTATION SECURITY CHECK
   ├── Verify no secrets in code
   ├── Check SQL queries are parameterized
   ├── Ensure proper input validation
   └── If issues found → Fix before completing

7. 🚨 SAVE MEMORY
   ├── Update active.md (ALWAYS — current state)
   ├── Update summary.md (if project shape changed)
   ├── Update components.md (if new components/hooks)
   ├── Update architecture.md (if structure changed)
   ├── Update changelog.md (dev changes)
   ├── Update decisions.md (if technical decisions made)
   └── Update agents-log.md (if agents delegated)

Read the full file on GitHub · 142 lines

Changes

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.

  1. 2d ago First seen · 142 lines · 13 tokens per session scan A 1572d05a05ef

Subscribe to this mod's changes

toh-dev is a command published in the GitHub repository wasintoh/toh-framework (95 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 1,074 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.