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/justhamade/triadjs/modelgit clone --depth 1 https://github.com/justhamade/triadjsWhat 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.00045 | $0.00567 |
| Opus 5 | $0.00023 | $0.00283 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
model 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the triad-schema skill for authoritative rules on t.model vs t.value, derivation operators, and .storage() hints.
Add a new model or value object to the project based on the user's description ($ARGUMENTS).
Steps
-
Decide model vs value object. Entities with identity →
t.model. Comparable-by-value shapes (Email, Money, DateRange) →t.value. If unsure, default tot.model. -
Place the file in
src/schemas/<resource>.ts. If a schemas directory doesn't exist, create it. -
Include derivations when appropriate:
CreateX = X.pick(...).named('CreateX')— omit identity/audit fields, keep user-supplied fieldsUpdateX = X.pick(...).partial().named('UpdateX')— make every updatable field optional
-
Identity field should have both
.identity()and.storage({ primaryKey: true })if the model will become a DB table:id: t.string().format('uuid').identity().storage({ primaryKey: true }) -
Add
.storage()hints to persistent fields per thetriad-drizzleskill:indexed,unique,references,defaultNow,defaultRandom,columnName. -
Update the bounded context's
models[]insrc/app.tssotriad validaterecognizes the model as part of the context's ubiquitous language. -
Run
triad validateto confirm the new model doesn't break any consistency checks. -
If the project uses persistence (
src/db/schema.generated.tsexists), runtriad db generateto regenerate the Drizzle schema.
Rules
- Always
.named('NewName')when deriving. Unnamed derivations collide with the parent in OpenAPI. - Never define a model inside a test file — tests import the real model.
- Value objects (
t.value) cannot be used withbody matchesassertions — only models can. - Use
t.datetime()rather thant.string().format('date-time'). - Use
t.empty()only for response slots (204/205/304), never for fields.
After adding the model, print the diff summary and suggest a follow-up: "Add an endpoint that uses <Model> via /triadjs:endpoint."
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 · 45 tokens per session scan A e858e5b00d39
model is a command published in the GitHub repository justhamade/triadjs (23 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 567 once invoked, about $0.0002 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.