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/dyeoman2/tanstack-start-template/validategit clone --depth 1 https://github.com/dyeoman2/tanstack-start-templateWhat 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.00000 | $0.00056 |
| Opus 5 | $0.00000 | $0.00028 |
| Sonnet 5 | $0.00000 | $0.00011 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
validate 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 today.
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.
What it actually says
run the commands one by one and resolve the errors. in order for the task to be successful, you need to be able to run all the commands without any errors or warnings:
- pnpm lint
- pnpm typecheck
- pnpm build
- pnpm dev
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.
- today First seen · 5 lines · 0 tokens per session scan A 1edecb10360d
validate is a command published in the GitHub repository dyeoman2/tanstack-start-template (26 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 56 tokens. 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-09-01.
Other commands, from other repositories
add
Add addons/features (PWA, Tauri, docs, linters, task runners, MCP, …) to an existing Better-T-Stack project via the Better-T-Stack MCP server.
scenario-testing
Review the tests in the current file or feature against the scenario-based testing mandate.
nodebench-qa
Full QA loop: crawl → findings → fix suggestions → re-crawl → savings report.
review-codex
Adversarial security review via OpenAI model — second opinion from a different AI.
sessions
Generate implementation session prompts from a PRD or research doc.
create-features
Create features from implementation plan.