agentmods.dev

validate

validate is a command for Claude Code from justhamade/triadjs. It costs 33 tokens per session (553 once invoked), scanned A, original, MIT.

A command that checks a TriadJS API description for consistency problems. It looks for issues such as duplicate endpoint names, duplicate routes, missing responses, and references to unknown models.

In plain words
What is it for?
Use it to check routes, endpoint names, response declarations, model references, and whether each bounded context uses only its own models.
Why use it?
It catches configuration and API-definition mistakes before they cause problems in generated clients or tests.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the triadjs plugin — 10 skills, 8 commands shipped together

not rated 24repo 6mo ago A scan 33 tokens original MIT

Good fit Use it to check routes, endpoint names, response declarations, model references, and whether each bounded context uses only its own models.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/justhamade/triadjs/validate
View source ↗ justhamade/triadjs
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.

Clone the repo
git clone --depth 1 https://github.com/justhamade/triadjs

Made for: Claude Code.

Or install triadjs, the plugin that ships this one along with the rest of its 10 skills, 8 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/justhamade/triadjs/validate/github.svg)](https://agentmods.dev/commands/justhamade/triadjs/validate)
Your own site
<a href="https://agentmods.dev/commands/justhamade/triadjs/validate"><img src="https://agentmods.dev/badge/commands/justhamade/triadjs/validate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for validate

Your own site · 80×15
<a href="https://agentmods.dev/commands/justhamade/triadjs/validate"><img src="https://agentmods.dev/badge/commands/justhamade/triadjs/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00033 $0.00553
Opus 5.5 $0.00013 $0.00221
Sonnet 5.5 $0.00007 $0.00111
Haiku 4.5 $0.00003 $0.00055

Measured 2mo ago against content hash 824cd186b770, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

plugin/commands/validate.md · 44 lines

How it starts

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

Load the triad-cli skill for command reference, and triad-endpoint or triad-schema depending on what the validator surfaces.

Run triad validate --strict and act on the output.

Steps

  1. Run triad validate --strict. If $ARGUMENTS contains --coverage, include it as well.

  2. Parse the output. The validator checks:

    1. No duplicate endpoint names (operationId collisions in OpenAPI)
    2. No duplicate METHOD path combinations
    3. Every endpoint declares at least one response
    4. Every response body matches <ModelName> assertion references a model that exists in the router
    5. Endpoints inside a bounded context only use models declared in that context's models[]

  3. For each finding, propose a specific fix:

Duplicate endpoint name

Rename the newer endpoint to something unique. OpenAPI uses name as operationId, so collisions produce silent bugs in generated clients.

Duplicate METHOD path

Two endpoints claim the same route. Usually a copy-paste mistake. Merge them or change one path.

Missing response

Every endpoint needs at least one entry in responses. Even a 204 needs responses: { 204: { schema: t.empty(), description: '...' } }.

Unknown model in assertion

A behavior uses 'response body matches Pet' but Pet isn't registered on the router (not reachable from any endpoint's request or response). Either add the model to an endpoint's schemas or rewrite the assertion to a different model.

Bounded-context leak (warning → error in --strict)

An endpoint inside router.context('Pets', { models: [Pet, ...] }) uses a model that isn't in models[]. Either add it to the context's models[] (if it legitimately belongs) or move the endpoint to the right context.

  1. After fixing, re-run triad validate --strict to confirm all issues cleared.

Rules

  • --strict turns warnings into errors — bounded-context leaks fail the build. Use --strict in CI.
  • --coverage warns about endpoints missing boundary coverage (schema constraints with no test hitting them). Add ...scenario.auto() to the endpoint's behaviors to fix.
  • Validator findings are rarely "just rewrite the code" — usually they surface real modeling bugs. Take each one seriously before suppressing it.

Read the full file on GitHub · 44 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. 2mo ago First seen · 44 lines · 33 tokens per session scan A 824cd186b770

Subscribe to this mod's changes

validate is a command published in the GitHub repository justhamade/triadjs (24 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 553 once invoked, about $0.0001 per session on Opus 5.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.

Backend and APIs
Related

validate compared with commands from other repositories

validate next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
validatejusthamade/triadjsCommand246mo agoMITA33Claude Code
initfcakyon/claude-codex-settingsCommand1.2ktodayApache-2.0A0Claude Code
http-serviceMadAppGang/magusCommand14todayMITA27Claude Code
buildAzure/ai-gatewayCommand511d agoMITA0Claude Code
api-contract-reviewMozurok/fhorja.devCommand1029d agoMITA64Claude Code
start-10-1minicoohei/ai-agent-campCommand3471mo agononeA2Claude Code
fastapimfmezger/ai_agent_dotfilesCommand73mo agoMITA84Claude Code, Gemini CLI