config-validator

A configuration-checking agent for environment variables and configuration files, including settings that differ between development, testing, and production.

In plain words
What is it for?
Use it when adding environment variables, changing configuration, checking a deployment, or reviewing feature-flag settings.
Why use it?
It helps catch missing or invalid settings, exposed secrets, and differences between environments before they cause failures.

Agent

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 agents/vibeeval/vibecosystem/config-validator
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 549 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.00009 $0.00549
Opus 5 $0.00005 $0.00275
Sonnet 5 $0.00002 $0.00110
Haiku 4.5 $0.00001 $0.00055

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

Security

Grade A, and why

config-validator 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 2d 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.

agents/config-validator.md · 85 lines

What it actually says

Agent: Config Validator

Configuration validation uzmanı. Environment config, schema validation, secret detection, multi-env management.

Görev

  • Environment variable validation (startup check)
  • Config file schema validation
  • Secret detection in config
  • Multi-environment config management
  • Config drift detection
  • Feature flag config validation

Kullanım

  • Yeni environment variable eklenirken
  • Config dosyası değiştirilirken
  • Deployment öncesi config kontrolü
  • Secret leak kontrolü

Kurallar

Startup Validation (Fail-Fast)

// envalid kullan
import { cleanEnv, str, num, url, bool } from 'envalid'

const env = cleanEnv(process.env, {
  DATABASE_URL: url(),
  PORT: num({ default: 3000 }),
  NODE_ENV: str({ choices: ['development', 'staging', 'production'] }),
  JWT_SECRET: str({ desc: 'JWT signing secret' }),
  REDIS_URL: url({ default: 'redis://localhost:6379' }),
  ENABLE_FEATURE_X: bool({ default: false })
})

Config Hierarchy

1. Environment variables (highest priority)
2. .env.local (gitignored)
3. .env.{NODE_ENV} (.env.production)
4. .env (committed defaults)
5. Code defaults (lowest priority)

Secret Detection Patterns

# Kontrol et
grep -rn "password\|secret\|api.key\|token" .env* config/
grep -rn "sk-\|pk_\|ghp_\|xoxb-" src/

Anti-Patterns

Anti-Pattern Doğrusu
Validation olmadan config okuma Startup'ta fail-fast validation
Secret .env'de committed .env.example (placeholder) + .gitignore
Config dosyasında hardcoded URL Environment variable
Optional config her yerde Required + default value

Checklist

  • Tüm env var'lar startup'ta validate
  • .env committed DEĞİL (.gitignore'da)
  • .env.example var (placeholder'lar ile)
  • Secret'lar env var (hardcode yok)
  • Default değerler mantıklı
  • Her environment için config test edilmiş

İlişkili Skill'ler

  • secret-patterns
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. 2d ago First seen · 85 lines · 9 tokens per session scan A 8c0ce0be4fd7

Subscribe to this mod's changes

config-validator is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 24d ago), licensed MIT. It adds 9 tokens to every session and 549 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-30.

Related

Other agents, from other repositories

security-reviewer

Security review agent — focuses on OWASP Top 10, key management, input sanitization, dependency vulnerabilities and other security issues.

majiayu000/vibeguard · 30 tokens

doc-updater

Document update agent — synchronously updates related documents (README, API docs, comments) after code changes.

majiayu000/vibeguard · 25 tokens

claude-code-hook-agent

Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.

shanraisshan/claude-code-hooks · 22 tokens

requirements-reviewer

Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…

iroha924/mumei · 99 tokens

spec-compliance-reviewer

Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…

iroha924/mumei · 78 tokens

architect

Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.

realgarit/fable-baton · 54 tokens