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 skills/justhamade/triadjs/triad-clinpx skills add justhamade/triadjs --skill triad-cligit 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.00064 | $0.01393 |
| Opus 5 | $0.00032 | $0.00696 |
| Sonnet 5 | $0.00013 | $0.00279 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
triad-cli 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI — command reference
The triad binary (from @triadjs/cli) dispatches to subcommands. Configs are discovered by walking upward from the cwd unless --config is passed.
Top-level flags (work on every subcommand)
| Flag | Purpose |
|---|---|
-c, --config <path> |
Override triad.config.ts path |
-r, --router <path> |
Override the router file (bypasses config) |
The CLI loads the config with jiti, so TypeScript configs work out-of-the-box without a build step.
triad test
Runs every behavior in the router as an in-process test. Also runs channel behaviors.
triad test
triad test --bail
triad test --filter createPet
| Flag | Effect |
|---|---|
--bail |
Stop on first failure |
--filter <pattern> |
Only run endpoints/channels whose name contains <pattern> |
Reads from config: test.setup, test.teardown, test.bail. Exits 1 if any scenario fails or errors.
Common failure modes:
servicesFactory failed→ yourtest-setup.tsdefault export throwsUnrecognized assertion: "..."→ yourthenphrase doesn't match the parser — see thetriad-behaviorsskillHandler returned status N which is not declared→ missing entry inresponsesResponse body for status N does not match declared schema→ handler output doesn't satisfy the declared schema
triad docs
Generates OpenAPI 3.1 from HTTP endpoints. Also writes an AsyncAPI 3.0 sibling file if the router has channels.
triad docs
triad docs --output ./generated/api.yaml
triad docs --format json
| Flag | Effect |
|---|---|
-o, --output <path> |
Output path (default: ./generated/openapi.yaml) |
-f, --format <format> |
yaml or json (defaults to file extension) |
Reads from config: docs.output, docs.format. When channels exist, writes asyncapi.yaml (or .json) beside the OpenAPI file.
Never hand-edit the output. The next
triad docsrun will blow away your edits. If you need something Triad doesn't model, use the OpenAPI generator'smergeoption programmatically (see@triadjs/openapi).
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 · 147 lines · 64 tokens per session scan A 534fed3b6f4f
triad-cli is a skill published in the GitHub repository justhamade/triadjs (23 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,393 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…