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 commands/basher83/lunar-claude/skill-validate-integrationgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/lunar-claude/skill-validate-integration)<a href="https://agentmods.dev/commands/basher83/lunar-claude/skill-validate-integration"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/skill-validate-integration.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.02906 |
| Opus 5 | $0.00000 | $0.01453 |
| Sonnet 5 | $0.00000 | $0.00581 |
| Haiku 4.5 | $0.00000 | $0.00291 |
Grade A, and why
skill-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 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.
How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slash Command Standards Compliance Review
File: plugins/meta/meta-claude/commands/skill/validate-integration.md Date: 2025-11-17 Reviewer: command-audit Agent Command Type: Plugin
Standards Reference
Source:
plugins/meta/claude-docs/skills/official-docs/reference/slash-commands.md
Key Requirements:
File Location (Lines 57-58, 71-72, 223):
- Project commands:
.claude/commands/directory - User commands:
~/.claude/commands/directory - Plugin commands:
commands/directory in plugin root
Frontmatter Fields (Lines 176-182):
description: Brief description (optional, defaults to first line)allowed-tools: Tool permissions (optional, inherits from conversation)argument-hint: Expected arguments (optional)model: Specific model (optional, inherits from conversation)disable-model-invocation: Prevent SlashCommand tool (optional, default false)
Arguments (Lines 96-126):
$ARGUMENTS: All arguments as single string$1,$2, etc.: Individual positional arguments
Bash Execution (Lines 129-150):
- Inline execution uses
!prefix:!`command` - Requires
allowed-tools: Bash(pattern:*)
File References (Lines 152-166):
- Use
@prefix:@path/to/file
Best Practices:
- Clear, specific instructions (not vague language)
- Written from Claude's perspective ("Your task is...")
- Examples for complex commands
- Single, clear purpose (Unix philosophy)
- KISS principle (Keep It Simple)
- YAGNI principle (You Aren't Gonna Need It)
Violations Found
VIOLATION #1: Bash Execution - Missing allowed-tools frontmatter
Current:
# Skill Validate Integration
Test skill integration with Claude Code ecosystem (conflict detection and compatibility).
(No frontmatter present)
Standard violated: Bash command execution requires allowed-tools: Bash(pattern:*) in frontmatter (slash-commands.md lines 130, 136)
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 · 453 lines · 0 tokens per session scan A 853d98b71bfa
skill-validate-integration is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,906 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.