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/anthropics/knowledge-work-plugins/searchnpx skills add anthropics/knowledge-work-plugins --skill searchgit clone --depth 1 https://github.com/anthropics/knowledge-work-pluginsWhat 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.00060 | $0.01471 |
| Opus 5 | $0.00030 | $0.00736 |
| Sonnet 5 | $0.00012 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
search 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- search — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Command
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Search across all connected MCP sources in a single query. Decompose the user's question, run parallel searches, and synthesize results.
Instructions
1. Check Available Sources
Before searching, determine which MCP sources are available. Attempt to identify connected tools from the available tool list. Common sources:
- ~~chat — chat platform tools
- ~~email — email tools
- ~~cloud storage — cloud storage tools
- ~~project tracker — project tracking tools
- ~~CRM — CRM tools
- ~~knowledge base — knowledge base tools
If no MCP sources are connected:
To search across your tools, you'll need to connect at least one source.
Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.
Supported sources: ~~chat, ~~email, ~~cloud storage, ~~project tracker, ~~CRM, ~~knowledge base,
and any other MCP-connected service.
2. Parse the User's Query
Analyze the search query to understand:
- Intent: What is the user looking for? (a decision, a document, a person, a status update, a conversation)
- Entities: People, projects, teams, tools mentioned
- Time constraints: Recency signals ("this week", "last month", specific dates)
- Source hints: References to specific tools ("in ~~chat", "that email", "the doc")
- Filters: Extract explicit filters from the query:
from:— Filter by sender/authorin:— Filter by channel, folder, or locationafter:— Only results after this datebefore:— Only results before this datetype:— Filter by content type (message, email, doc, thread, file)
3. Decompose into Sub-Queries
For each available source, create a targeted sub-query using that source's native search syntax:
~~chat:
- Use available search and read tools for your chat platform
- Translate filters:
from:maps to sender,in:maps to channel/room, dates map to time range filters - Use natural language queries for semantic search when appropriate
- Use keyword queries for exact matches
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.
- 2d ago First seen · 179 lines · 60 tokens per session scan A 5330512ac1f7
search is a skill published in the GitHub repository anthropics/knowledge-work-plugins (23,791 stars, last pushed today), licensed Apache-2.0. It adds 60 tokens to every session and 1,471 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…