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/benshapyro/cadre-devkit-claude/validategit clone --depth 1 https://github.com/benshapyro/cadre-devkit-claudeWrote 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/benshapyro/cadre-devkit-claude/validate)<a href="https://agentmods.dev/commands/benshapyro/cadre-devkit-claude/validate"><img src="https://agentmods.dev/badge/commands/benshapyro/cadre-devkit-claude/validate.svg" alt="Measured on agentmods" 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 | $0.00004 | $0.00742 |
| Opus 5 | $0.00002 | $0.00371 |
| Sonnet 5 | $0.00001 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
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 3d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Command
Purpose: Quantitative validation - runs automated checks (types, lint, tests, build).
Distinct from /review: This command runs automated tooling. Use /review first for qualitative code review (style, security, best practices).
Workflow: /review → /validate → /ship
Run all validations before shipping code. Automatically detects the project's tech stack and runs only relevant checks.
1. Detect Tech Stack
First, check which config files exist to determine the project type:
package.json→ Node.js/TypeScript projecttsconfig.json→ TypeScriptpyproject.tomlorrequirements.txt→ PythonCargo.toml→ Rustgo.mod→ Go
Use Glob to check for these files before running language-specific checks.
2. Run Relevant Checks
TypeScript/Node.js (if package.json exists)
Type checking:
!npx tsc --noEmit 2>&1 || true
Linting (if lint script exists):
!npm run lint 2>&1 || true
Tests:
!npm test 2>&1 || true
Build:
!npm run build 2>&1 || true
Python (only if pyproject.toml or requirements.txt exists)
Linting:
!ruff check . 2>&1 || true
Type checking:
!mypy . 2>&1 || true
Tests:
!pytest -q 2>&1 || true
Rust (only if Cargo.toml exists)
Check:
!cargo check 2>&1 || true
Clippy:
!cargo clippy -- -D warnings 2>&1 || true
Tests:
!cargo test 2>&1 || true
Go (only if go.mod exists)
Build:
!go build ./... 2>&1 || true
Vet:
!go vet ./... 2>&1 || true
Tests:
!go test ./... 2>&1 || true
3. SelfCheck Protocol
Answer these questions with evidence:
Q1: Are tests passing?
- Show actual test output
- Report pass/fail counts
Q2: Are all requirements met?
- Map requirements to implementation
- Confirm nothing missed
Q3: No unverified assumptions?
- External APIs verified
- Libraries documented
Q4: Is there evidence?
- Include validation output
- Show build success
Report Format
## Validation Report
### Tech Stack Detected
[List detected languages/frameworks]
### Type Checking
[✅ Passed / ❌ Failed / ⏭️ Skipped (not applicable)]
[Details if failed]
### Linting
[✅ Passed / ❌ Failed / ⏭️ Skipped (not applicable)]
[Details if failed]
### Tests
[✅ X passed, Y failed / ❌ Failed to run / ⏭️ Skipped]
[Failure details if any]
### Build
[✅ Passed / ❌ Failed / ⏭️ Skipped (not applicable)]
[Details if failed]
### Summary
[READY TO SHIP / NEEDS FIXES]
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.
- 3d ago First seen · 129 lines · 4 tokens per session scan A 0e7418cf2d09
validate is a command published in the GitHub repository benshapyro/cadre-devkit-claude (9 stars, last pushed 9mo ago), licensed MIT. It adds 4 tokens to every session and 742 once invoked, about $0.0000 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-31.
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.
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.