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.
git clone --depth 1 https://github.com/athola/skrillsWrote 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/athola/skrills/search-skills)<a href="https://agentmods.dev/commands/athola/skrills/search-skills"><img src="https://agentmods.dev/badge/commands/athola/skrills/search-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/commands/athola/skrills/search-skills"><img src="https://agentmods.dev/badge/commands/athola/skrills/search-skills.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00284 |
| Opus 5 | $0.00005 | $0.00142 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
search-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 11d 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
Search Skills
Search installed skills using the skrills MCP server.
Use the mcp__plugin_skrills_skrills__search-skills-fuzzy tool with:
query: Search query (required)threshold: Similarity threshold 0.0-1.0 (lower = more results)limit: Maximum results to returninclude_description: Also search descriptions (default: true)
Parse $ARGUMENTS:
- First argument or quoted string: search query
--threshold Nor-t N: Similarity threshold (default: 0.3)--limit Nor-l N: Max results (default: 10)--name-only: Only search skill names, not descriptions
Report search results including:
- Skill name and location
- Match score
- Brief description
- Source (Claude, Codex, Copilot)
Handle errors:
- If query empty: Prompt for search query
- If no matches found: Suggest broader search or lower threshold
- If index unavailable: Report and suggest re-indexing
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.
- 11d ago First seen · 33 lines · 10 tokens per session scan A fa8373de64ff
search-skills is a command published in the GitHub repository athola/skrills (69 stars, last pushed 7d ago), licensed MIT. It adds 10 tokens to every session and 284 once invoked, about $0.0001 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 commands, from other repositories
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
prompt-optimizer
Analyze and rewrite a prompt to maximize clarity, specificity, and output quality.
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.