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/liaogui1023/coding-plugin/find-skillsnpx skills add liaogui1023/coding-plugin --skill find-skillsgit clone --depth 1 https://github.com/liaogui1023/coding-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/liaogui1023/coding-plugin/find-skills)<a href="https://agentmods.dev/skills/liaogui1023/coding-plugin/find-skills"><img src="https://agentmods.dev/badge/skills/liaogui1023/coding-plugin/find-skills.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.00056 | $0.00882 |
| Opus 5 | $0.00028 | $0.00441 |
| Sonnet 5 | $0.00011 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Skills (Windows Version)
Helps users discover and install agent skills from the open ecosystem when they need new capabilities.
When to Use
Activate this skill when users:
- Ask "how do I do X" or "can you do X" for specialized tasks
- Request "find a skill for X"
- Want to extend agent capabilities in specific domains
- Use Chinese keywords to search (auto-translate to English)
Core Workflow
1. Handle Chinese Input
If user input contains Chinese, translate it to English first:
| Chinese | English |
|---|---|
| 网页开发 | web development |
| 测试 | testing |
| 部署 | deploy |
| 文档 | documentation |
| 代码审查 | code review |
| 设计 | design |
| 工作流 | workflow |
Example: User asks "找一个React测试的skill" → Search for "react testing"
2. Search for Skills
npx skills find [query]
Or in CMD:
npx skills find [query]
3. Present Results
For each result, provide:
- Skill name and purpose
- Installation command
- Link to https://skills.sh/ for details
4. Install if Requested
npx skills add <owner/repo@skill> -g -y
Common Search Categories
| Category | Keywords |
|---|---|
| Web Dev | react, nextjs, vue, angular, frontend |
| Testing | jest, playwright, cypress, testing |
| DevOps | deploy, docker, kubernetes, ci-cd |
| Documentation | readme, changelog, docs |
| Code Quality | review, lint, format |
| Design | ui, accessibility, css |
| Productivity | workflow, git, automation |
Search Optimization Strategy
Ranking Metrics
The skills.sh directory ranks skills by:
| View | Description | Use Case |
|---|---|---|
| All Time | Total install count | Find proven, stable skills |
| Trending (24h) | Recent 24-hour activity | Discover new popular skills |
| Hot | Current trending | Find what's popular right now |
Recommended Search Priority
- Prefer high-install skills - Skills with 10K+ installs are battle-tested
- Check trending for new solutions - Emerging skills may solve newer problems
- Prioritize verified sources -
vercel-labs/agent-skillsis highly trusted
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 · 124 lines · 56 tokens per session scan A a73f1371b5f2
find-skills is a skill published in the GitHub repository liaogui1023/coding-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 882 once invoked, about $0.0003 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
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…