Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/vodailocz/kilo-kit-mcp/validate-skill)<a href="https://agentmods.dev/commands/vodailocz/kilo-kit-mcp/validate-skill"><img src="https://agentmods.dev/badge/commands/vodailocz/kilo-kit-mcp/validate-skill.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.00000 | $0.00318 |
| Opus 5 | $0.00000 | $0.00159 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
validate-skill 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 6d 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.
What it actually says
🔍 Validate Skill Command
Usage: Validate skill files for correctness, completeness, and quality.
Quick Start
# Python
python src/tools/validate-skill.py skills/kilo-kit/debugging/systematic/
python src/tools/validate-skill.py skills/kilo-kit/ --all --verbose
# Node.js
node src/tools/validate-skill.js skills/kilo-kit/debugging/systematic
node src/tools/validate-skill.js --all skills/kilo-kit --verbose
What It Checks
Required (Error if missing)
- SKILL.md file exists
- YAML frontmatter with
name,description,version - Sections: "When to Use", "Process", "Guidelines"
Recommended (Warning if missing)
- Frontmatter:
behaviors,token_estimate,dependencies - Sections: "Prerequisites", "Success Criteria", "Related Skills"
- At least 3 keywords in description
Quality (Info)
- File size (not too short or too long)
- Process has multiple phases
- Guidelines has DO and DON'T subsections
Options
| Flag | Description |
|---|---|
--all, -a |
Validate all skills under path |
--verbose, -v |
Show all issues including info |
--json |
Output as JSON (Python only) |
--fix |
Attempt auto-fix (planned) |
Validate Skill Command v1.0.0
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.
- 6d ago First seen · 46 lines · 0 tokens per session scan A da0c40c8bcc3
validate-skill is a command published in the GitHub repository VoDaiLocz/kilo-kit-mcp (26 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 318 tokens. 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 commands, from other repositories
new
Plan mode. Generates a plan for a feature based on a description.
feature
Create a feature specification using spec-driven development.
milestone-list
PitWay: List every milestone with a concise one-line status.
help
Analyze workflow state and provide context-aware guidance with visual progress indicators and recommended next steps.
wb-notify
Load directions via mcpwork-buddywbrun("agentdocs", {"path": "notifications/notify-directions", "depth": "full"}), then call the capability.
wb-project-list
Load directions via mcpwork-buddywbrun("agentdocs", {"path": "projects/project-list-directions", "depth": "full"}), then call the capability.