skill-git:search

A command that searches online skill libraries, including SkillHub and ClawHub, for skills matching a query or resembling a local skill.

In plain words
What is it for?
Use it to search for a skill by topic or find online alternatives similar to one you already have.
Why use it?
It helps you find an existing skill when you need a capability that is not already installed.

Command

Install

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.

agentmods
npx agentmods add commands/knowledgexlab/skill-git/search
Clone the repo
git clone --depth 1 https://github.com/KnowledgeXLab/skill-git
Per session 66 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,018 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.05018
Opus 5 $0.00033 $0.02509
Sonnet 5 $0.00013 $0.01004
Haiku 4.5 $0.00007 $0.00502

Measured yesterday against content hash bca0275293cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skill-git:search scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

From `search_query`, extract 2–3 meaningful keywords by removing stop words and generic terms (e.g. "a", "the", "find", "skill", "功能", "一个", "做", "帮我"). Each keyword may be a single word or a two-word phrase — never thre
commands/search.md · 474 lines

How it starts

The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are running /skill-git:search. Follow these steps exactly.

All output shown to the user must be in English.

Tool Loading

Before doing any work, load all required tools in a single ToolSearch call:

select:TaskCreate,TaskUpdate,TaskList,AskUserQuestion

Do not issue multiple ToolSearch calls.

Task Tracking

You MUST create a task for each item below and update each task's status as you progress (pending → in_progress → completed):

  1. Detect intent — parse $ARGUMENTS to determine mode, agent, and search query
  2. Init check — validate local skill exists (similar mode only)
  3. Build search query — use $ARGUMENTS directly (query mode) or extract from local skill (similar mode)
  4. Search registries — query SkillHub and ClawHub in parallel
  5. Enrich ClawHub results — fetch download counts from detail endpoint (similar mode: also filter locally installed skills)
  6. Filter and rank — score candidates, select top 5
  7. Present results — display summary table and detail blocks
  8. Offer to install — prompt user to pick and install a result

Step 0 — Intent Detection

Interpret $ARGUMENTS as natural language. Determine:

  • mode: query or similar

    • similar if the user references a local skill they want to find online equivalents for (e.g. "something like my code-review", "类似我本地 tdd 的", "enhance my humanizer")
    • query otherwise (user describes what they want to find)
  • similar_skill: the local skill name, if mode = similar; otherwise null

  • search_query: the search keywords, if mode = query; for similar mode, this is not set here — it is built in Step 2

  • agent: which agent's skill directory to use (default: claude; detect from phrases like "for gemini", "gemini 的", "on codex", etc.) — detected in all modes for consistency, but only used to resolve skill paths in similar mode

    agent base_dir
    claude ~/.claude
    gemini ~/.gemini
    codex ~/.codex
    openclaw ~/.openclaw

Read the full file on GitHub · 474 lines

Changes

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.

  1. yesterday First seen · 474 lines · 66 tokens per session scan A bca0275293cc

Subscribe to this mod's changes

skill-git:search is a command published in the GitHub repository KnowledgeXLab/skill-git (41 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 5,018 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.