Borrowing it
Nothing to install: this file belongs to Agent-Threat-Rule/agent-threat-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Agent-Threat-Rule/agent-threat-rules/main/.claude/commands/scan-skill.mdgit clone --depth 1 https://github.com/Agent-Threat-Rule/agent-threat-rulesWrote 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/agent-threat-rule/agent-threat-rules/scan-skill)<a href="https://agentmods.dev/commands/agent-threat-rule/agent-threat-rules/scan-skill"><img src="https://agentmods.dev/badge/commands/agent-threat-rule/agent-threat-rules/scan-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.00334 |
| Opus 5 | $0.00000 | $0.00167 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
scan-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 8d 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
Scan Specific Skill
Scan a specific MCP skill by npm package name or GitHub URL.
Input
$ARGUMENTS — npm package name (e.g. mcp-server-filesystem) or GitHub URL
Steps
- If argument is a GitHub URL, extract the npm package name from package.json
- Run single-package audit:
cd /Users/user/Downloads/agent-threat-rules && npx tsx scripts/audit-npm-skills-v2.ts --limit 1 --offset 0 --output "data/scan-single-$(date +%Y%m%d%H%M%S).json"
Note: For single package scanning, we need to create a temporary registry entry. Instead:
cd /Users/user/Downloads/agent-threat-rules
mkdir -p /tmp/atr-single-scan
npm pack $ARGUMENTS --pack-destination /tmp/atr-single-scan 2>/dev/null
- If the package downloads successfully, run the ATR engine against it
- Present findings using the "Plain Language Consequences" template (T3):
- What the skill claims to do
- What it actually does (each finding in plain language)
- What consequences the user faces
- ATR rules triggered
- If CRITICAL or HIGH:
- Generate a Skills Sec post draft using templates from
templates/post-templates.json - Ask: "Post this? Which platforms?"
- Generate a Skills Sec post draft using templates from
- If CLEAN:
- Report clean status
- Ask if I want to add to whitelist
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.
- 8d ago First seen · 36 lines · 0 tokens per session scan A c4606731137b
scan-skill is a command published in the GitHub repository Agent-Threat-Rule/agent-threat-rules (385 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 334 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
brin-scan
Scan a package, repo, MCP server, domain, web page, or skill for security threats using the brin API.
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.