agentmods.dev

validate

validate is a skill for Claude Code from mordilion/ai-instructions-and-prompts. It costs 27 tokens per session (1,658 once invoked), scanned A, original, MIT.

A validation skill for checking the ai-iap plugin's configuration and collections of rules, processes, extensions, and subagents. It reports each check as a pass or failure with details.

In plain words
What is it for?
Use it after changing the plugin's configuration or rule library, or when diagnosing problems with custom rules, processes, schemas, and project state.
Why use it?
It finds missing files, invalid configuration, broken references, and other integrity problems before they affect users.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ai-iap plugin — 2 skills, 5 agents shipped together

not rated 1repo 2mo ago A scan 27 tokens original MIT

Good fit Use it after changing the plugin's configuration or rule library, or when diagnosing problems with custom rules, processes, schemas, and project state.

Compare 6 skills from other repositories ↓
View source ↗ mordilion/ai-instructions-and-prompts
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add mordilion/ai-instructions-and-prompts
Claude Code
/plugin install ai-iap

Made for: Claude Code.

Or install ai-iap, the plugin that ships this one along with the rest of its 2 skills, 5 agents.

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 validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/mordilion/ai-instructions-and-prompts/validate/github.svg)](https://agentmods.dev/skills/mordilion/ai-instructions-and-prompts/validate)
Your own site
<a href="https://agentmods.dev/skills/mordilion/ai-instructions-and-prompts/validate"><img src="https://agentmods.dev/badge/skills/mordilion/ai-instructions-and-prompts/validate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for validate

Your own site · 80×15
<a href="https://agentmods.dev/skills/mordilion/ai-instructions-and-prompts/validate"><img src="https://agentmods.dev/badge/skills/mordilion/ai-instructions-and-prompts/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,658 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00027 $0.01658
Opus 5 $0.00014 $0.00829
Sonnet 5 $0.00005 $0.00332
Haiku 4.5 $0.00003 $0.00166

Measured 10d ago against content hash ec8000fdbe58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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 10d 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.

plugin/skills/validate/SKILL.md · 161 lines

How it starts

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

AI Instructions & Prompts Validation

Run validation checks on the plugin's configuration and rule library.

Important Paths

  • Config: ${CLAUDE_PLUGIN_ROOT}/lib/config.json
  • Config schema: ${CLAUDE_PLUGIN_ROOT}/lib/config.schema.json
  • Config extend schema: ${CLAUDE_PLUGIN_ROOT}/lib/config.extend.schema.json
  • Rule library: ${CLAUDE_PLUGIN_ROOT}/lib/rules/
  • Process library: ${CLAUDE_PLUGIN_ROOT}/lib/processes/
  • Custom extensions: ${CLAUDE_PLUGIN_ROOT}/custom/
  • Custom config: ${CLAUDE_PLUGIN_ROOT}/custom/config.extend.json
  • Custom rules: ${CLAUDE_PLUGIN_ROOT}/custom/rules/
  • Custom processes: ${CLAUDE_PLUGIN_ROOT}/custom/processes/
  • Custom subagents: ${CLAUDE_PLUGIN_ROOT}/custom/claude-subagents.extend.json
  • State file (in user project): .ai-iap-state.json

Validation Checks

Run all checks below and report results as [PASS] or [FAIL] with details.

1. Config File Validation

  1. Read ${CLAUDE_PLUGIN_ROOT}/lib/config.json — must exist and be valid JSON.
  2. Validate against ${CLAUDE_PLUGIN_ROOT}/lib/config.schema.json:
    • Must have version (string, semver pattern).
    • Must have tool object with name, outputDir, outputFile, fileExtension.
    • Must have languages object.
  3. Each language must have: name, globs, alwaysApply (boolean), description, files (array).
  4. general language must have alwaysApply: true.
  5. No language other than general should have alwaysApply: true (warn).
  6. globs must be a string, not an array.
  7. No obsolete enabled property on any language.

2. Rule File Existence

For each language in config:

  1. For each entry in files[], verify ${CLAUDE_PLUGIN_ROOT}/lib/rules/{lang}/{file}.md exists.
  2. For each optionalRules entry, verify the referenced file exists.
  3. For each framework, verify ${CLAUDE_PLUGIN_ROOT}/lib/rules/{lang}/frameworks/{fw_file}.md exists.
  4. For each structure, verify ${CLAUDE_PLUGIN_ROOT}/lib/rules/{lang}/frameworks/structures/{struct_file}.md exists.
  5. If tool.outputFileSource is set, verify ${CLAUDE_PLUGIN_ROOT}/lib/rules/general/{source}.md exists.

Read the full file on GitHub · 161 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. 10d ago First seen · 161 lines · 27 tokens per session scan A ec8000fdbe58

Subscribe to this mod's changes

validate is a skill published in the GitHub repository mordilion/ai-instructions-and-prompts (1 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,658 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-08-31.

Debugging
Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens