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/iplug3/audio-plugin-dev-skills/validate-clapnpx skills add iPlug3/audio-plugin-dev-skills --skill validate-clapgit clone --depth 1 https://github.com/iPlug3/audio-plugin-dev-skillsWrote 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/iplug3/audio-plugin-dev-skills/validate-clap)<a href="https://agentmods.dev/skills/iplug3/audio-plugin-dev-skills/validate-clap"><img src="https://agentmods.dev/badge/skills/iplug3/audio-plugin-dev-skills/validate-clap.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 | $0.00061 | $0.01400 |
| Opus 5 | $0.00030 | $0.00700 |
| Sonnet 5 | $0.00012 | $0.00280 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
validate-clap 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 4d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAP Validator
Plugin Install Locations
clap-validator accepts a direct path, but these are the standard install locations where hosts scan for CLAP plugins.
| Platform | User Location | System Location |
|---|---|---|
| macOS | ~/Library/Audio/Plug-Ins/CLAP/ |
/Library/Audio/Plug-Ins/CLAP/ |
| Windows | %LOCALAPPDATA%\Programs\Common\CLAP\ |
C:\Program Files\Common Files\CLAP\ |
| Linux | ~/.clap/ |
/usr/lib/clap/ or /usr/local/lib/clap/ |
Instructions
- Install
clap-validator(see Installation below) - Locate the built
.clapplugin bundle (in your build output directory or one of the standard locations above) - Run:
clap-validator validate /path/to/plugin.clap - To see only failures:
clap-validator validate --only-failed /path/to/plugin.clap - For debugging, run a specific test in-process:
clap-validator validate --in-process --test-filter <test> /path/to/plugin.clap
Installation
Option 1: Download Pre-built Binary
- Download from GitHub Releases
- Extract and place in your PATH:
- macOS / Linux:
/usr/local/bin/ - Windows: Add to
PATHor place in project directory
- macOS / Linux:
macOS only: Builds are unsigned. Remove the quarantine attribute:
xattr -dr com.apple.quarantine /path/to/clap-validator
Option 2: Build from Source
# Requires Rust (all platforms)
cargo install clap-validator
# Or build from source
git clone https://github.com/free-audio/clap-validator
cd clap-validator
cargo build --release
# Binary at target/release/clap-validator (macOS/Linux)
# Binary at target\release\clap-validator.exe (Windows)
Basic Usage
# Validate a CLAP plugin
clap-validator validate /path/to/plugin.clap
# Show only failed tests
clap-validator validate --only-failed /path/to/plugin.clap
# Validate multiple plugins
clap-validator validate /path/to/plugin1.clap /path/to/plugin2.clap
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.
- 4d ago First seen · 179 lines · 61 tokens per session scan A 784fc5280d9c
validate-clap is a skill published in the GitHub repository iPlug3/audio-plugin-dev-skills (88 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 1,400 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-30.
Other skills, from other repositories
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
simple
Summarize short user notes into clear action items.
agent-ready-cloudflare
Audit and improve website readiness for AI agents using the Cloudflare "Is It Agent Ready?" scanner (isitagentready.com). Covers scanning via API, interpreting results, generating implementation prompts, and fixing every check. Use when the user mentions "agent ready", "isitagentready", "AI agent scan", "agent…
aidlc-master
Runs the AWS AI-DLC (AI-Driven Development Life Cycle) methodology end to end: an adaptive three-phase workflow (Inception → Construction → Operations) with human approval gates, a full audit trail, and all artifacts in aidlc-docs/. Use when the user says "Using AI-DLC", "AI-DLC", "AIDLC", "aidlc-master", or asks for…
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
security-specialist
Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".