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.
git clone --depth 1 https://github.com/basher83/agent-auditorWrote 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/commands/basher83/agent-auditor/validate-integration)<a href="https://agentmods.dev/commands/basher83/agent-auditor/validate-integration"><img src="https://agentmods.dev/badge/commands/basher83/agent-auditor/validate-integration/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.
<a href="https://agentmods.dev/commands/basher83/agent-auditor/validate-integration"><img src="https://agentmods.dev/badge/commands/basher83/agent-auditor/validate-integration.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.02280 |
| Opus 5.5 | $0.00006 | $0.00912 |
| Sonnet 5.5 | $0.00003 | $0.00456 |
| Haiku 4.5 | $0.00001 | $0.00228 |
Grade A, and why
validate-integration 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 1mo 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Validate Integration
Test skill integration with Claude Code ecosystem (conflict detection and compatibility).
Usage
/meta-claude:skill:validate-integration $ARGUMENTS
Arguments:
$1: Path to the skill directory to validate (required)
What This Does
Validates that the skill integrates cleanly with the Claude Code ecosystem:
- Naming Conflicts: Verifies no duplicate skill names exist
- Functionality Overlap: Checks for overlapping descriptions/purposes
- Command Composition: Tests compatibility with slash commands
- Component Integration: Validates interaction with other meta-claude components
- Ecosystem Fit: Ensures skill complements existing capabilities
Note: This is integration validation - it tests ecosystem compatibility, not runtime behavior.
Instructions
Your task is to perform integration validation checks on the skill at the provided path.
Step 1: Verify Skill Exists
Verify that the skill directory contains a valid SKILL.md file:
!test -f "$1/SKILL.md" && echo "SKILL.md exists" || echo "Error: SKILL.md not found"
If SKILL.md does not exist, report error and exit.
Step 2: Extract Skill Metadata
Read the SKILL.md frontmatter to extract key metadata. The frontmatter format is:
---
name: skill-name
description: Skill description text
---
Extract the following from the skill at $1/SKILL.md:
- Skill name
- Skill description
- Any additional metadata fields
Use this metadata for conflict detection and overlap analysis.
Step 3: Check for Naming Conflicts
Search for existing skills with the same name across the marketplace.
Find all SKILL.md files:
!find "$(git rev-parse --show-toplevel)/plugins" -type f -name "SKILL.md"
For each existing skill, perform the following analysis:
- Extract the skill name from frontmatter
- Compare with the new skill's name (from
$1/SKILL.md) - If names match, record as a naming conflict
Detect these types of conflicts:
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.
- 1mo ago First seen · 355 lines · 14 tokens per session scan A 5e4d710ad51d
validate-integration is a command published in the GitHub repository basher83/agent-auditor (5 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 2,280 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.