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 skills/rjmurillo/ai-agents/validation-authoritynpx skills add rjmurillo/ai-agents --skill validation-authoritygit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/validation-authority)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/validation-authority"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/validation-authority.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.00036 | $0.01165 |
| Opus 5 | $0.00018 | $0.00583 |
| Sonnet 5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
validation-authority 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Authority
When integrating external validators (PSScriptAnalyzer, markdownlint, ESLint, etc.), respect upstream defaults. Modify local configuration to match upstream behavior. Do not modify upstream tool code.
Triggers
Activate when:
- Validation fails unexpectedly
- Before modifying validator behavior or configuration
- When tempted to change upstream tool source code
- When adding a new external validator to the project
- When suppressing validator warnings without rationale
Decision Tree
Validation failure occurred
|
v
Is the validator upstream (external tool)?
| |
YES NO (local/custom)
| |
v v
Modify LOCAL config Modify tool as needed
to align with tool (you own the code)
|
v
Document override rationale
in config comments
Process
- Classify the validator: Determine if the tool is upstream (external) or local (project-owned).
- Identify the conflict: Find the specific rule or default causing the failure.
- Check upstream defaults: Read the tool's documentation for the default behavior.
- Align local config: Update project configuration files to match or explicitly override upstream defaults.
- Document overrides: Add comments explaining why any override differs from the upstream default.
Trigger Table
| Scenario | Action | Example |
|---|---|---|
| PSScriptAnalyzer rule fails | Update .psscriptanalyzerrc.psd1 |
Suppress PSAvoidUsingWriteHost with rationale |
| markdownlint rule fails | Update .markdownlint.yaml |
Disable MD013 line-length for generated docs |
| ESLint rule conflicts | Update .eslintrc |
Override no-console for CLI tools |
| Upstream tool has a bug | File issue upstream, add workaround in config | Pin tool version, suppress specific rule |
| Tool default changed after upgrade | Review and align local config to new default | Update config after major version bump |
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.
- 2d ago First seen · 144 lines · 36 tokens per session scan A 0b8799627fe9
validation-authority is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,165 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-09-03.
Other skills, from other repositories
loop-triage
Triage recent CI failures, open issues, and recent commits into a prioritized, actionable picture. Reads the prior STATE.md as memory and rewrites it. The maker half of the loop.
ci-triage
How to find out why a GitHub Actions run failed, and how to tell a real failure from a flake or an infrastructure problem. Use when a check is red, a workflow is stuck, or a run needs re-running.
manage-skills
세션 변경사항을 분석하여 검증 스킬 누락을 탐지합니다. 기존 스킬을 동적으로 탐색하고, 새 스킬을 생성하거나 기존 스킬을 업데이트한 뒤 프로젝트 CLAUDE.md를 관리합니다.
ci-cd
GitHub Actions CI/CD 파이프라인 설계 및 자동화.
gha
Analyze GitHub Actions failures and identify root causes.
ast-refactoring
AST 기반 안전한 코드 리팩토링 스킬.