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 klh/speedy-claude --skill skill-lookupgit clone --depth 1 https://github.com/klh/speedy-claudeWrote 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/klh/speedy-claude/skill-lookup)<a href="https://agentmods.dev/skills/klh/speedy-claude/skill-lookup"><img src="https://agentmods.dev/badge/skills/klh/speedy-claude/skill-lookup/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/klh/speedy-claude/skill-lookup"><img src="https://agentmods.dev/badge/skills/klh/speedy-claude/skill-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00548 |
| Opus 5 | $0.00026 | $0.00274 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
skill-lookup 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 6d 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
Workflow
- Search for skills matching the user's request using
search_skills - Present results with title, description, author, and file list
- If the user picks a skill, retrieve it with
get_skillto get all files - Install by saving files to
.claude/skills/{slug}/and verify the SKILL.md exists - Confirm installation and explain what the skill does and when it activates
Example
search_skills({"query": "code review", "limit": 5, "category": "coding"})
get_skill({"id": "abc123"})
Available Tools
Use these prompts.chat MCP tools:
search_skills- Search for skills by keywordget_skill- Get a specific skill by ID with all its files
How to Search for Skills
Call search_skills with:
query: The search keywords from the user's requestlimit: Number of results (default 10, max 50)category: Filter by category slug (e.g., "coding", "automation")tag: Filter by tag slug
Present results showing:
- Title and description
- Author name
- File list (SKILL.md, reference docs, scripts)
- Category and tags
- Link to the skill
How to Get a Skill
Call get_skill with:
id: The skill ID
Returns the skill metadata and all file contents:
- SKILL.md (main instructions)
- Reference documentation
- Helper scripts
- Configuration files
How to Install a Skill
When the user asks to install a skill:
- Call
get_skillto retrieve all files - Create the directory
.claude/skills/{slug}/ - Save each file to the appropriate location:
SKILL.md→.claude/skills/{slug}/SKILL.md- Other files →
.claude/skills/{slug}/{filename}
- Read back
SKILL.mdto verify the frontmatter is intact
Guidelines
- Always search before suggesting the user create their own skill
- Present search results in a readable format with file counts
- When installing, confirm the skill was saved successfully
- Explain what the skill does and when it activates
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.
- 6d ago Changed · +2 lines a5cdc34e4d5e
- 10d ago First seen · 77 lines · 51 tokens per session scan A a848c17efd09
skill-lookup is a skill published in the GitHub repository klh/speedy-claude (11 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 548 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-30.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…