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 skills/lifedever/skills-plugin/skill-scannpx skills add lifedever/skills-plugin --skill skill-scangit clone --depth 1 https://github.com/lifedever/skills-pluginWrote 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/lifedever/skills-plugin/skill-scan)<a href="https://agentmods.dev/skills/lifedever/skills-plugin/skill-scan"><img src="https://agentmods.dev/badge/skills/lifedever/skills-plugin/skill-scan.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 | $0.00165 | $0.01874 |
| Opus 5 | $0.00082 | $0.00937 |
| Sonnet 5 | $0.00033 | $0.00375 |
| Haiku 4.5 | $0.00016 | $0.00187 |
Grade A, and why
skill-scan 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 4d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-scan
Discover and recommend across the user's locally installed skills. Solves the "I have too many skills installed and don't remember which one to use" problem.
Step 1 — Always scan first
Run the scan script to get the current inventory. Pass through the working directory so project-level skills are included:
bash "${CLAUDE_SKILL_DIR}/scripts/scan.sh"
Output is TSV (name\tsource\tpath\tdescription) on stdout, plus a one-line summary on stderr. Sources: project, personal, or plugin:<plugin-name>. Same-named skills are deduplicated by priority (project > personal > plugin).
If the summary says scanned 0 skills, tell the user and stop — likely no install. Otherwise, continue.
Step 2 — Decide mode from the user's phrasing
| User said | Mode |
|---|---|
| "list / browse / 有哪些 / 清单" type | List |
| Describes a scenario / asks "which skill for X" | Recommend |
| Ambiguous | Ask once: list, or scenario-based recommendation? |
List mode
Emit a categorized inventory. Rules:
-
No preamble. Don't say "Here are your skills" — go straight into categories.
-
Detect current project context, then order categories by relevance. In
${PROJECT_DIR:-$PWD}, check for:- Claude config:
CLAUDE.md,AGENTS.md,.claude/,.claude-plugin/ - Repo marker:
.git/ - Language manifests:
package.json,Package.swift,Cargo.toml,go.mod,pyproject.toml,requirements.txt,Gemfile,pom.xml,build.gradle,composer.json - Container:
Dockerfile,docker-compose.yml
Project mode — any of the above exist:
- Read
CLAUDE.md(if present) plus the manifest filenames you found; infer the specific project type (e.g. "macOS Swift app", "Vue frontend", "Claude Code skills plugin", "Rust CLI", "Node monorepo"). - Order: categories most-aligned with that project type first → general/utility categories middle → unrelated categories last.
- Stat-line suffix:
· 已按当前项目（<inferred-type>）相关性排序.
- Claude config:
What ships with it
1 file 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.
- 4d ago First seen · 137 lines · 165 tokens per session scan A d34c3f6c571d
skill-scan is a skill published in the GitHub repository lifedever/skills-plugin (11 stars, last pushed 13d ago), licensed MIT. It adds 165 tokens to every session and 1,874 once invoked, about $0.0008 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…