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/channelgit 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.00039 | $0.00918 |
| Opus 5 | $0.00019 | $0.00459 |
| Sonnet 5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
channel 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the triad-channel skill for the authoritative channel() signature and state typing rules. Load triad-behaviors for channel-specific assertion phrases.
Add a new WebSocket channel to the project based on the user's description ($ARGUMENTS).
Prerequisites
- Confirm the project uses
@triadjs/fastify— Express and Hono adapters do NOT support channels. If the project is on a non-Fastify adapter, tell the user and stop. - Install
@fastify/websocketif not already present:npm install @fastify/websocket.
Steps
-
Place the channel in
src/channels/<name>.ts. -
Define the state interface and use the phantom witness pattern:
interface ChatRoomState { userId: string; userName: string; roomId: string; } channel({ state: {} as ChatRoomState, // phantom — value ignored, type used for ctx.state // ... });Without the witness,
ctx.stateisRecord<string, any>. -
Declare
clientMessages(what clients send) andserverMessages(what the server emits). EveryclientMessageskey must have a matchinghandlers[key]— missing or extra keys are compile errors. -
Implement
onConnect— validate the handshake (via schemas orctx.reject(code, msg)), seedctx.state, optionally broadcast a join event. -
Implement
onDisconnect— optionally broadcast a leave event. Don't throw. -
Implement per-message handlers — call repositories via
ctx.services, then:ctx.broadcast.eventName(payload)to send to everyone including the senderctx.broadcastOthers.eventName(payload)to exclude the senderctx.send.eventName(payload)to reply only to this client
-
If the channel is browser-facing, use
auth.strategy: 'first-message'— browsers cannot set custom headers onnew WebSocket(). Declare an__authclient message and castctx.authPayloadinsideonConnect. -
Add channel behaviors:
behaviors: [ scenario('broadcasting a message reaches every client') .given('two connected clients') .setup(async () => ({ /* ... */ })) .when('alice sends a sendMessage') .then('all clients receive a message event') .and('bob receives a message with text "hello"'), ]Use channel-specific phrases from the
triad-behaviorsskill —<client> receives a <type> event,all clients receive...,connection is rejected with code N.
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 · 79 lines · 39 tokens per session scan A 1e5ca1581b18
channel is a command published in the GitHub repository justhamade/triadjs (23 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 918 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.