search

search is a skill for Claude Code from joestump/claude-plugin-sdd. It costs 58 tokens per session (4,002 once invoked), scanned A, original, MIT.

A search workflow that explores a codebase’s documentation and source code together. It can find design records and specifications, then show how related code calls one another.

In plain words
What is it for?
Finding architecture decisions, specifications, authentication logic, payment flows, related modules, and the functions involved in a particular behaviour.
Why use it?
It helps locate both the written decision and the code affected by it, which is useful when ordinary text search misses connections.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the sdd plugin — 19 skills shipped together

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add joestump/claude-plugin-sdd
Claude Code
/plugin install sdd

Made for: Claude Code.

Or install sdd, the plugin that ships this one along with the rest of its 19 skills.

Wrote 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.

agentmods badge for search

README.md
[![agentmods](https://agentmods.dev/badge/skills/joestump/claude-plugin-sdd/search.svg)](https://agentmods.dev/skills/joestump/claude-plugin-sdd/search)
Your own site
<a href="https://agentmods.dev/skills/joestump/claude-plugin-sdd/search"><img src="https://agentmods.dev/badge/skills/joestump/claude-plugin-sdd/search.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,002 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.1 $0.00058 $0.04002
Opus 5 $0.00029 $0.02001
Sonnet 5 $0.00012 $0.00800
Haiku 4.5 $0.00006 $0.00400

Measured 2d ago against content hash bf32010f2839, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

skills/search/SKILL.md · 319 lines

How it starts

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

Harness portability. This skill runs on any agent harness that loads Agent Skills — Claude Code, Codex CLI, OpenCode, Crush. Tool names used below (AskUserQuestion, Task, TeamCreate, SendMessage, TaskCreate, ToolSearch, mcp__*, ${CLAUDE_PLUGIN_ROOT}) denote capabilities, not hard requirements: map each to your harness's equivalent or use the documented fallback per ${CLAUDE_PLUGIN_ROOT}/references/harness-compat.md. References to CLAUDE.md mean the project memory file (CLAUDE.md, AGENTS.md, or CRUSH.md) per harness-compat § "Project Memory File". A citation of the form shared-patterns.md § "Section" names one ## heading in that file — load only that section (see its "How to Read This File" note), never the whole file.

Search ADRs, specs, and code simultaneously using qmd hybrid retrieval, then enrich results with cgg call graphs for deeper code exploration.

Process

  1. Handle no-args / --help: If $ARGUMENTS is empty or contains --help, output the usage block below and stop:

    Usage: /sdd:search <query> [--output markdown|json] [--unfiltered] [--module <name>]
    
    Examples:
      /sdd:search "JWT authentication"
      /sdd:search "payment processing" --output json
      /sdd:search "token validation" --unfiltered
      /sdd:search "auth middleware" --module api
    
    Searches ADRs, specs, and code with qmd hybrid retrieval, then generates
    call graphs with cgg for the most relevant code matches.
    
  2. Parse arguments: Extract from $ARGUMENTS:

    • <query>: everything before any -- flags (required; stop here if empty after flag extraction)
    • --output markdown|json: output format (default: markdown)
    • --unfiltered: when present, skip filter derivation and pass raw query keywords to cgg
    • --module <name>: when present, scope all collections and cgg to that module

Read the full file on GitHub · 319 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. 2d ago Changed bf32010f2839
  2. 6d ago First seen · 319 lines · 58 tokens per session scan A 0b43f27663b4

Subscribe to this mod's changes

search is a skill published in the GitHub repository joestump/claude-plugin-sdd (32 stars, last pushed 2d ago), licensed MIT. It adds 58 tokens to every session and 4,002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens