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 skills add jmagly/aiwg --skill config-validatorgit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/skills/jmagly/aiwg/config-validator)<a href="https://agentmods.dev/skills/jmagly/aiwg/config-validator"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/config-validator.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.1 | $0.00015 | $0.02535 |
| Opus 5 | $0.00008 | $0.01267 |
| Sonnet 5 | $0.00003 | $0.00507 |
| Haiku 4.5 | $0.00002 | $0.00253 |
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.
How it starts
The opening of the file, as written. The whole thing — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "validate [YAML/JSON]" in configuration context → config schema check
- "is this valid config" → configuration validation
Purpose
This skill ensures AIWG projects are properly configured by:
- Validating YAML/JSON configuration syntax
- Checking required fields and values
- Verifying file references and paths
- Detecting configuration conflicts
- Recommending fixes for issues
Behavior
When triggered, this skill:
-
Locates configuration files:
- Scan for AIWG config files
- Identify framework configs
- Find project-specific configs
-
Validates syntax:
- Parse YAML/JSON files
- Check for syntax errors
- Validate structure against schema
-
Checks completeness:
- Verify required fields present
- Check for missing sections
- Validate cross-references
-
Verifies references:
- Check file paths exist
- Validate agent references
- Verify template paths
-
Detects conflicts:
- Duplicate definitions
- Conflicting settings
- Incompatible options
-
Generates report:
- List all issues found
- Severity classification
- Fix recommendations
Configuration Files Validated
AIWG Core Configs
aiwg_configs:
project_config:
path: .aiwg/config/project.yaml
schema: schemas/project-config.schema.yaml
required_fields:
- project_name
- project_type
- phase
team_profile:
path: .aiwg/team/team-profile.yaml
schema: schemas/team-profile.schema.yaml
required_fields:
- team_name
- members
risk_register:
path: .aiwg/risks/risk-register.yaml
schema: schemas/risk-register.schema.yaml
required_fields:
- risks
artifact_config:
path: .aiwg/config/artifacts.yaml
schema: schemas/artifact-config.schema.yaml
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 · 510 lines · 15 tokens per session scan A bea180491ae6
config-validator is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 2,535 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
parallax-core
Apply session-safe Parallax reasoning and verification to code changes.
typescript-circular-dependency
Detect and resolve TypeScript/JavaScript circular import dependencies. Use when: (1) "Cannot access 'X' before initialization" at runtime, (2) Import returns undefined unexpectedly, (3) "ReferenceError: Cannot access X before initialization", (4) Type errors that disappear when you change import order, (5) Jest/Vitest…
nextjs-server-side-error-debugging
Debug getServerSideProps and getStaticProps errors in Next.js. Use when: (1) Page shows generic error but browser console is empty, (2) API routes return 500 with no details, (3) Server-side code fails silently, (4) Error only occurs on refresh not client navigation. Check terminal/server logs instead of browser for…
agent-introspection-debugging
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.