Borrowing it
Nothing to install: this file belongs to terrene-foundation/metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/terrene-foundation/metis/main/.claude/commands/validate.mdgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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.
[](https://agentmods.dev/commands/terrene-foundation/metis/validate)<a href="https://agentmods.dev/commands/terrene-foundation/metis/validate"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/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.
<a href="https://agentmods.dev/commands/terrene-foundation/metis/validate"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01006 |
| Opus 5.5 | $0.00000 | $0.00402 |
| Sonnet 5.5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00101 |
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 1mo 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.
This is a copy
94% identical to validate — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate - Project Compliance Validation
Purpose
Run compliance checks against the project's applicable standards. Automatically detects project type and applies the right validation rules.
Step 1: Detect Project Type
Before validating, determine what frameworks the project uses:
- Check for Kailash SDK (Python): Look for
kailashinrequirements.txt,pyproject.toml,setup.py,setup.cfg, orfrom kailash/import kailashin Python files - Check for Kailash SDK (Rust with Python bindings): Look for
kailashinCargo.tomldependencies alongside Python project markers - Generic project: If neither detected, apply universal standards only
Report what you detected before proceeding.
Step 2: Universal Checks (ALL projects)
These always apply regardless of project type:
| Check | Rule Source | What It Validates |
|---|---|---|
| Security | rules/security.md |
No hardcoded secrets, parameterized queries, input validation, output encoding |
| No Stubs | rules/zero-tolerance.md |
No TODOs, placeholders, NotImplementedError, simulated data in production code |
| Env Variables | rules/env-models.md |
API keys and model names from .env only, never hardcoded |
| Testing Policy | rules/testing.md |
Real infrastructure recommended in Tier 2-3 tests, real infrastructure required |
| Git Hygiene | rules/git.md |
Conventional commits, no secrets in history, atomic commits |
Universal Validation Checklist
- No hardcoded secrets (API keys, passwords, tokens)
- No SQL/code injection vulnerabilities
- All user input validated at system boundaries
- No TODOs, stubs, or placeholder code in production files
- API keys and model names sourced from
.env - No mocking in integration/E2E tests
- Error handling present (no silent
except: pass) - No secrets in git history
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.
- 1mo ago First seen · 90 lines · 0 tokens per session scan A c4786f7fef7a
validate is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,006 tokens. A static security scan graded it A with 0 findings. It is 94% identical to validate, differing in 19 lines, and is treated as a copy.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.