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 volcengine/volcengine-skills --skill volcengine-find-skillsgit clone --depth 1 https://github.com/volcengine/volcengine-skillsWrote 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/volcengine/volcengine-skills/volcengine-find-skills)<a href="https://agentmods.dev/skills/volcengine/volcengine-skills/volcengine-find-skills"><img src="https://agentmods.dev/badge/skills/volcengine/volcengine-skills/volcengine-find-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/volcengine/volcengine-skills/volcengine-find-skills"><img src="https://agentmods.dev/badge/skills/volcengine/volcengine-skills/volcengine-find-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 76 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00128 | $0.01002 |
| Opus 5 | $0.00064 | $0.00501 |
| Sonnet 5 | $0.00026 | $0.00200 |
| Haiku 4.5 | $0.00013 | $0.00100 |
Grade A, and why
volcengine-find-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 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcengine Skills Finder
Use the bundled catalog to inspect every available skill and select the minimum skill set that covers the request. Treat plugin ownership as catalog classification only; install exact skills.
Decision flow
- Detect whether the request starts with skill discovery or whether an active Volcengine task has reached a capability gap in the currently loaded or installed skills.
- Preserve completed work and pause only the unsupported part of the active task.
- List the complete catalog without changing installation state.
- Inspect every name, product domain, summary, and keyword, then select the minimum exact skill set that covers the user's request. Make the selection directly when the catalog provides enough information.
- Pass only exact skill names to the installer. Use plugin ownership to explain classification, never as the installation target.
- Install through the
skillsCLI and verify the resulting installed state. Never report success from process exit alone. - If the host cannot load a newly installed skill into the current thread, tell the user to start a new thread and restate the original task plus completed context.
List and select skills
Run the script relative to this skill directory:
python3 scripts/find_skills.py list
python3 scripts/find_skills.py list --json
python3 scripts/find_skills.py info <skill-or-plugin>
Always read the complete list output before selecting a skill. Use --json when keywords or the
English summaries help distinguish related skills. Choose by responsibility rather than name alone;
install multiple skills only when the request crosses distinct responsibilities.
The catalog includes all four skills in skills/core/ and every optional skill owned directly by a
product-domain plugin. skills/specialized/<domain>/<skill>/ contains generated copies of those
optional skills, grouped by the plugin name without volcengine-; each skill is listed only once
in the catalog. If none of the listed responsibilities covers the request, report that the
repository does not currently provide a matching skill.
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.
- 4d ago Changed · +2 lines 0494dc0b7eef
- 11d ago First seen · 99 lines · 128 tokens per session scan A 9efeebb5a2a7
volcengine-find-skills is a skill published in the GitHub repository volcengine/volcengine-skills (19 stars, last pushed 4d ago), licensed MIT. It adds 128 tokens to every session and 1,002 once invoked, about $0.0006 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…