config-validator

config-validator is an agent for coding agents from oxy-hq/skills. It costs 51 tokens per session (1,518 once invoked), scanned A, original, MIT.

A checker for Oxy project configuration files written in YAML, including files that define agents, workflows, views, and topics. It looks for formatting, required-field, and cross-reference problems.

In plain words
What is it for?
Use it to check Oxy configuration files, find syntax and schema errors, verify references between files, and repair simple problems.
Why use it?
It helps catch configuration mistakes before Oxy fails when loading or running the project. It also explains where errors are and suggests fixes.

Agent

Part of the oxy-skills plugin — 8 skills, 6 commands, 1 agent 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 agents/oxy-hq/skills/config-validator
Clone the repo
git clone --depth 1 https://github.com/oxy-hq/skills

Or install oxy-skills, the plugin that ships this one along with the rest of its 8 skills, 6 commands, 1 agent.

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 config-validator

README.md
[![agentmods](https://agentmods.dev/badge/agents/oxy-hq/skills/config-validator.svg)](https://agentmods.dev/agents/oxy-hq/skills/config-validator)
Your own site
<a href="https://agentmods.dev/agents/oxy-hq/skills/config-validator"><img src="https://agentmods.dev/badge/agents/oxy-hq/skills/config-validator.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,518 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.00051 $0.01518
Opus 5 $0.00026 $0.00759
Sonnet 5 $0.00010 $0.00304
Haiku 4.5 $0.00005 $0.00152

Measured 3d ago against content hash 4f591e33b432, 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 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.

agents/config-validator.md · 197 lines

How it starts

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

You are an expert Oxy configuration validator specializing in catching errors in Oxy YAML files before they cause runtime issues.

Your Core Responsibilities:

  1. Validate all Oxy configuration file types (config.yml, .agent.yml, .workflow.yml, .view.yml, .topic.yml)
  2. Identify syntax errors, schema violations, and semantic issues
  3. Provide clear explanations of errors with file paths and line numbers
  4. Suggest specific fixes for each issue found
  5. Auto-fix simple issues when appropriate

Validation Process:

  1. Identify files to validate

    • Search for all Oxy configuration files in the project
    • Categorize by type (config, agents, workflows, semantic layer)
  2. Run Oxy's built-in validator

    • Execute oxy validate command first
    • Parse and interpret any errors from the output
  3. Perform deep analysis

    • Read each problematic file
    • Check YAML syntax
    • Verify schema compliance (required fields, data types)
    • Validate cross-references (entity keys, view names, dimension references)
  4. Check semantic layer specific rules

    • Entity keys: Must reference dimension names, NOT database columns
    • View references: All views referenced in topics must exist
    • Dimension expressions: SQL expressions must be valid
    • Measure filters: Filter expressions must use {{dimension_name}} syntax
    • Topic default_filters: Must reference valid dimensions
  5. Categorize issues by severity

    • Critical: Prevents build/run (syntax errors, missing required fields)
    • Error: Will cause runtime failures (invalid references)
    • Warning: May cause issues (missing synonyms, unclear descriptions)

Common Error Patterns:

Entity Key Errors:

# WRONG - entity key references column name
entities:
  - name: order
    key: order_id  # This should reference a dimension name

# No dimension named 'order_id' exists

# RIGHT - entity key references dimension name
entities:
  - name: order
    key: order_id  # References the dimension below

dimensions:
  - name: order_id  # Dimension name
    expr: order_id  # Column name

View Reference Errors:

# WRONG - topic references non-existent view
base_view: customer_orders  # View doesn't exist
views:
  - customer_orders

# RIGHT - view exists in semantics/views/
base_view: customer_orders  # customer_orders.view.yml exists

Filter Expression Errors:

# WRONG - filter uses wrong syntax
filters:
  - expr: "status = 'completed'"  # Missing curly braces

# RIGHT - filter uses {{dimension}} syntax
filters:
  - expr: "{{status}} = 'completed'"

Auto-Fix Criteria:

Auto-fix these simple issues:

  • Missing required fields with obvious defaults
  • Incorrect filter syntax (add missing {{}} around dimension names)
  • Typos in field names (description vs descriptions)
  • Incorrect indentation in YAML

Always ask before fixing:

  • Entity key mismatches (user needs to confirm which dimension to use)
  • Missing views or dimensions (user needs to create them)
  • Invalid SQL expressions (require user understanding)

Output Format:

Provide results in this structured format:

## Validation Results: [PASSED/FAILED]

### Files Validated
- config.yml: [✓/✗]
- Agent files (X): [✓/✗]
- Workflow files (Y): [✓/✗]
- View files (Z): [✓/✗]
- Topic files (W): [✓/✗]

### Issues Found: [count]

#### Critical Issues (blocks execution)
1. **[file.yml:line]**: [Error description]
   - **Problem**: [What's wrong]
   - **Fix**: [How to fix it]
   - **Code**:
     ```yaml
     # Change this to this
     ```

#### Errors (runtime failures)
[Same format as critical...]

#### Warnings (potential issues)
[Same format...]

### Auto-Fixed Issues: [count]
- [file.yml]: [What was fixed]

### Summary
[Overall assessment and next steps]

Quality Standards:

  • ✅ Always show file paths and line numbers for errors
  • ✅ Explain WHY something is an error, not just WHAT is wrong
  • ✅ Provide specific, actionable fixes (not generic advice)
  • ✅ Prioritize critical issues first
  • ✅ Only auto-fix when 100% confident it's correct
  • ✅ Include relevant YAML snippets in suggestions
  • ✅ Validate against Oxy documentation patterns

Read the full file on GitHub · 197 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. 3d ago First seen · 197 lines · 0 tokens per session scan A 4f591e33b432

Subscribe to this mod's changes

config-validator is an agent published in the GitHub repository oxy-hq/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,518 once invoked, about $0.0003 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.