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 skills add yu-iskw/skill-inspector --skill inspect-skillsgit clone --depth 1 https://github.com/yu-iskw/skill-inspectorWrote 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/yu-iskw/skill-inspector/inspect-skills)<a href="https://agentmods.dev/skills/yu-iskw/skill-inspector/inspect-skills"><img src="https://agentmods.dev/badge/skills/yu-iskw/skill-inspector/inspect-skills/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/skills/yu-iskw/skill-inspector/inspect-skills"><img src="https://agentmods.dev/badge/skills/yu-iskw/skill-inspector/inspect-skills.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.00036 | $0.00446 |
| Opus 5 | $0.00018 | $0.00223 |
| Sonnet 5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
inspect-skills 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.
What it actually says
Inspect Agent Skills
Purpose
Run the skill-inspector CLI to analyze one or more Agent Skills for spec compliance, security (e.g. RCE, data exfiltration), and provider compatibility. Use this skill when you need to validate, audit, or harden Agent Skills.
When to Use
- The user asks to "inspect skills", "validate skills", "audit skills for security", or "check skill compliance".
- You need to verify a skill directory or repo before adopting or recommending it.
- You want a 0–100 score and actionable findings for a skill or skill set.
How to Use
-
List skills only (no LLM required): From the repo or directory that contains skills, run:
./scripts/list-skills.sh [source]Example:
./scripts/list-skills.sh .or./scripts/list-skills.sh owner/repo. -
Full inspection (requires at least one LLM API key): Run:
./scripts/inspect.sh [source] [options]The script checks for
ANTHROPIC_API_KEY,OPENAI_API_KEY,GOOGLE_API_KEY,MISTRAL_API_KEY, orGROQ_API_KEYand exits with a clear error if none are set.Examples:
./scripts/inspect.sh .— inspect all skills in current directory./scripts/inspect.sh ./my-skill --provider anthropic./scripts/inspect.sh owner/repo -s "skill-name" --json
-
Interpret results: See references/cli-usage.md for score ranges, severity levels, and
--jsonoutput.
Resources
- CLI usage and options: Flags, providers, and environment variables.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 46 lines · 36 tokens per session scan A cc187f069660
inspect-skills is a skill published in the GitHub repository yu-iskw/skill-inspector (2 stars, last pushed 10d ago), licensed Apache-2.0. It adds 36 tokens to every session and 446 once invoked, about $0.0002 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.
Other skills, from other repositories
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
implementing-semgrep-for-custom-sast-rules
Write custom Semgrep SAST rules in YAML to detect application-specific vulnerabilities, enforce coding standards, and integrate into CI/CD pipelines.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.