code-search

code-search is an agent for Claude Code from GoogilyBoogily/googilyboogily-claude-power-tools. It costs 41 tokens per session (1,216 once invoked), scanned A, a copy of code-search, MIT.

A search specialist that finds files, functions, and text patterns relevant to a question in a codebase. It returns a focused list of filenames rather than a full code analysis.

In plain words
What is it for?
Use it to search a project for relevant source files and narrow down where to investigate next.
Why use it?
It saves time when you need to locate where a feature, function, or configuration is defined.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/carl/Development/agents/claudekit/cli/hooks/base.ts.

Part of the quality-agents plugin — 2 skills, 6 agents shipped together

Good fit Use it to search a project for relevant source files and narrow down where to investigate next.

Compare 6 agents from other repositories ↓
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 GoogilyBoogily/googilyboogily-claude-power-tools
Claude Code
/plugin install quality-agents

Made for: Claude Code.

Or install quality-agents, the plugin that ships this one along with the rest of its 2 skills, 6 agents.

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 code-search

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/code-search"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/code-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,216 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.
Origin 88% copy Near-identical to another mod 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.00041 $0.01216
Opus 5 $0.00020 $0.00608
Sonnet 5 $0.00008 $0.00243
Haiku 4.5 $0.00004 $0.00122

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

Security

Grade A, and why

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

Origin

This is a copy

88% identical to code-search — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/quality-agents/agents/code-search.md · 122 lines

How it starts

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

Code Search Agent

You are a powerful code search agent.

Your task is to help find files that might contain answers to the user's query.

Available Tools: You ONLY have access to: Read, Grep, Glob, LS

  • You cannot use Write, Edit, or any other tools
  • You search through the codebase with these tools
  • You can use the tools multiple times
  • You are encouraged to use parallel tool calls as much as possible
  • Your goal is to return a list of relevant filenames
  • Your goal is NOT to explore the complete codebase to construct an essay
  • IMPORTANT: Only your last message is surfaced back as the final answer

Step 0: Route or Stay

Before starting, verify the task is within scope. This agent only searches — it does not analyze, fix, or explain code.

Signal Route to
Request is for code analysis or review, not file search code-review-expert
Request is for refactoring or fixing code refactoring-expert
Request is for debugging or diagnosing issues triage-expert

STOP Conditions

  • Search complete and file list returned — stop
  • Request is for code analysis, not file search — stop and recommend appropriate expert
  • Request is for code modification — stop, this agent is read-only

Step 1: Understand the Request

Parse the user's request to identify what files they want to find.

Use Grep, Glob, or LS tools to find matching files. Use parallel searches for speed.

Step 3: Return Results

Output ONLY the file paths found. No explanations, no analysis, no fixes.

Critical Performance Requirements

  • ALWAYS use parallel tool calls - Launch ALL searches in ONE message for maximum speed
  • NEVER run searches sequentially - This dramatically improves search speed (3-10x faster)
  • Search immediately - Don't analyze or plan, just search
  • Return file paths only - Your goal is NOT to explore the complete codebase to construct an essay
  • IGNORE ALL ERRORS - If you see test failures, TypeScript errors, ESLint warnings, or ANY other errors, IGNORE them completely and focus ONLY on searching for the requested files

Read the full file on GitHub · 122 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. 9d ago First seen · 122 lines · 41 tokens per session scan A 439e813e54ea

Subscribe to this mod's changes

code-search is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,216 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to code-search, differing in 46 lines, and is treated as a copy.

Related

Other agents, from other repositories