gauntlex:validate

gauntlex:validate is a skill for Claude Code, Codex from sanjoy1234/gauntlex. It costs 48 tokens per session (409 once invoked), scanned A, original, MIT.

A dry-run command that checks whether a GAUNTLEX security-testing setup is ready without launching attacks.

In plain words
What is it for?
Use it to validate a specification, configured model provider, vulnerability test gate, knowledge store, and policy playbooks.
Why use it?
It finds missing model settings, files, playbooks, storage access, or validation fixtures before a real run.

Skill for Claude CodeCodex

Part of the gauntlex plugin — 7 skills, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/sanjoy1234/gauntlex/validate
Any agent
npx skills add sanjoy1234/gauntlex --skill validate
Clone the repo
git clone --depth 1 https://github.com/sanjoy1234/gauntlex

Made for: Claude Code, Codex.

Or install gauntlex, the plugin that ships this one along with the rest of its 7 skills, 1 MCP server.

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 gauntlex:validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/sanjoy1234/gauntlex/validate.svg)](https://agentmods.dev/skills/sanjoy1234/gauntlex/validate)
Your own site
<a href="https://agentmods.dev/skills/sanjoy1234/gauntlex/validate"><img src="https://agentmods.dev/badge/skills/sanjoy1234/gauntlex/validate.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 409 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.00409
Opus 5 $0.00024 $0.00204
Sonnet 5 $0.00010 $0.00082
Haiku 4.5 $0.00005 $0.00041

Measured 4d ago against content hash eff17989395c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gauntlex: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 4d 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.

.claude/skills/gauntlex/validate/SKILL.md · 41 lines

What it actually says

/gauntlex:validate

Validates the GAUNTLEX environment and spec WITHOUT firing any real attacks.

Usage

/gauntlex:validate [--spec <file>]

Execution

gauntlex validate --spec "$SPEC_FILE"

What It Checks

  1. AVF gate: Breaker must find >75% of seeded vulnerabilities in the 5 golden CVE fixtures
  2. Model reachability: GAUNTLEX never assumes a provider — it checks whichever provider was explicitly configured (Anthropic, OpenRouter, HuggingFace, OpenAI-compatible, or local Ollama, set via gauntlex setup, MODEL_PROVIDER, or .gauntlex.yml). If nothing is configured, this fails with "not configured — run gauntlex setup"
  3. ChromaDB: Knowledge Forge writable at .gauntlex/forge/
  4. Playbook resolution: All domains listed in .gauntlex.yml have corresponding YAML files
  5. Spec parseable: The spec file (if provided) can be read and is non-empty

Output to User

Report each check as PASS/FAIL with a reason, using the exact Detail text from the command output for the model check — do not assume or guess a provider. If any FAIL:

  • Explain the specific failure
  • Give the fix command shown in the output (gauntlex setup if no provider is configured at all; otherwise the provider-specific fix, e.g. ollama pull llama3.1:8b only if Ollama is the provider actually configured)

If all pass: "Environment validated — ready to run."

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. 4d ago First seen · 41 lines · 48 tokens per session scan A eff17989395c

Subscribe to this mod's changes

gauntlex:validate is a skill published in the GitHub repository sanjoy1234/gauntlex (1 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 409 once invoked, about $0.0002 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.