search-tools

search-tools is a skill for Claude Code from parcadei/Continuous-Claude-v3. It costs 7 tokens per session (491 once invoked), scanned A, original, MIT.

A decision guide for choosing among code-search tools based on whether you need to find meaning, code structure, or exact text.

In plain words
What is it for?
Use it to search concepts such as how authentication works, find function calls or usages for refactoring, and locate literal text, names, or regular expressions in a codebase.
Why use it?
It helps avoid using the wrong search method for the question you are asking, while providing a built-in text-search fallback when optional tools are unavailable.

Skill for Claude Code

Written for Claude Code: PreToolUse hook event.

not rated 3.9krepo +3 7mo ago A scan Socket: passSnyk: passSkillSpector: pass 7 tokens original MIT

Good fit Use it to search concepts such as how authentication works, find function calls or usages for refactoring, and locate literal text, names, or regular expressions in a codebase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/parcadei/continuous-claude-v3/search-tools
About the project

Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.

parcadei/Continuous-Claude-v3 · 3,937 stars · on GitHub

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.

Any agent
npx skills add parcadei/Continuous-Claude-v3 --skill search-tools
Clone the repo
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3

Made for: Claude Code.

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-tools

README.md
[![agentmods](https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/search-tools/github.svg)](https://agentmods.dev/skills/parcadei/continuous-claude-v3/search-tools)
Your own site
<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/search-tools"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/search-tools/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.

agentmods 80×15 button for search-tools

Your own site · 80×15
<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/search-tools"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/search-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 15 Feb 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00007 $0.00491
Opus 5 $0.00003 $0.00246
Sonnet 5 $0.00001 $0.00098
Haiku 4.5 $0.00001 $0.00049

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

Security

Grade A, and why

search-tools 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 9d 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.

.claude/skills/archive/search-tools/SKILL.md · 72 lines

What it actually says

Search Tool Hierarchy

When searching code, use this decision tree:

Decision Tree

Need CONCEPTUAL/SEMANTIC search?
  (how does X work, find patterns, understand architecture)
  → Use LEANN (/leann-search) - embedding-based semantic search
  → PreToolUse hook auto-redirects semantic Grep queries

Need to understand code STRUCTURE?
  (find function calls, class usages, refactor patterns)
  → Use AST-grep (/ast-grep-find)

Need to find TEXT in code?
  → Use Morph (/morph-search) - 20x faster
  → If no Morph API key: fall back to Grep tool

Simple one-off search?
  → Use built-in Grep tool directly

Tool Comparison

Tool Best For Requires
LEANN Semantic search: "how does caching work", "error handling patterns", conceptual queries Index built
AST-grep Structural patterns: "find all calls to foo()", refactoring, find usages by type MCP server
Morph Fast text search: "find files mentioning error", grep across codebase API key
Grep Literal patterns, class/function names, regex Nothing (built-in)

Examples

LEANN (semantic/conceptual):

  • "how does authentication work"
  • "find error handling patterns"
  • "where is rate limiting implemented"

AST-grep (structural):

  • "Find all functions that return a Promise"
  • "Find all React components using useState"
  • "Refactor all imports of X to Y"

Morph (text search):

  • "Find all files mentioning 'authentication'"
  • "Search for TODO comments"

Grep (literal):

  • class ProviderAdapter
  • def __init__
  • Regex patterns

LEANN Commands

# Search with semantic query
leann search opc-dev "how does blackboard communication work" --top-k 5

# List available indexes
leann list

# Rebuild index (when code changes)
leann build opc-dev --docs dir1 dir2 --no-recompute --no-compact --force
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. 9d ago First seen · 72 lines · 7 tokens per session scan A f3c85a70c261

Subscribe to this mod's changes

search-tools is a skill published in the GitHub repository parcadei/Continuous-Claude-v3 (3,937 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 491 once invoked, about $0.0000 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

prove-checks

Prove a passing check was capable of failing before recording it as evidence. Use when a test, CI job, build-and-diff, smoke test or rehearsal comes back green and that green is about to be treated as proof - especially when the check depends on a setup mutation (a sed/awk rewrite, an env var, a secret, a fixture…

sergeyklay/.agents · 221 tokens

headsup-diagnose

Actively test the Codex headsup stack by flashing idle, working, and waiting tab colors and checking daemon application.

wasulajr/headsup · 30 tokens

headsup-status

Print a read-only health snapshot for the Codex headsup hook stack: daemon, watchdog, sessions, notifications, and logs.

wasulajr/headsup · 30 tokens

debugging-and-recovery

Use when something is broken, a test is failing, behavior is wrong, when investigating a production incident, when a user reports a bug, when a feature works locally but not in another environment, or when the system behaves differently than the contract specifies.

aneja5/forge-skills · 56 tokens

prod-debug

Production debugging skill. Pre-loads DB schema, container registry, and prod environment facts from .claude/prod-debug/ in the current project root. Use when the user invokes /prod-debug or /prod-debug bootstrap.

josephfung/trimkit · 48 tokens

error-handling-and-resilience

Use when establishing error handling patterns for a project, when adding retry logic, circuit breakers, or graceful degradation, when reviewing how a service handles failures, or when an incident reveals that a failure mode was silently swallowed.

aneja5/forge-skills · 50 tokens