search-code

search-code is a skill for Claude Code, Codex from marmot-protocol/agent-config. It costs 27 tokens per session (800 once invoked), scanned A, original, MIT.

A code-search guide for finding definitions, usages, and recurring patterns in a software repository. It covers common code forms in JavaScript, TypeScript, Python, and Go.

In plain words
What is it for?
Finding functions, classes, types, imports, API endpoints, error handling, and environment-variable references in a codebase.
Why use it?
It reduces the time spent browsing unfamiliar files or sorting through too many search results. It also helps narrow searches when you need to find where something is defined or used.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { handleAuth } from '../auth/handler'.

Good fit Finding functions, classes, types, imports, API endpoints, error handling, and environment-variable references in a codebase.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/marmot-protocol/agent-config
agentmods
npx agentmods add skills/marmot-protocol/agent-config/search-code

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/marmot-protocol/agent-config/search-code/github.svg)](https://agentmods.dev/skills/marmot-protocol/agent-config/search-code)
Your own site
<a href="https://agentmods.dev/skills/marmot-protocol/agent-config/search-code"><img src="https://agentmods.dev/badge/skills/marmot-protocol/agent-config/search-code/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-code

Your own site · 80×15
<a href="https://agentmods.dev/skills/marmot-protocol/agent-config/search-code"><img src="https://agentmods.dev/badge/skills/marmot-protocol/agent-config/search-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 800 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 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.00027 $0.00800
Opus 5.5 $0.00011 $0.00320
Sonnet 5.5 $0.00005 $0.00160
Haiku 4.5 $0.00003 $0.00080

Measured 1mo ago against content hash d2d6d67b8ae6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

search-code 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 1mo 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.

opencode/skills/search-code/SKILL.md · 155 lines

How it starts

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

Search Code Skill

You are an expert at finding code in repositories quickly and accurately.

Activation

This skill activates when:

  • User asks to find code, functions, or patterns
  • User wants to locate definitions or usages
  • User asks "where is" or "find" questions
  • Context involves code navigation

Search Strategies

Finding Definitions

Functions/Methods:

# JavaScript/TypeScript
function\s+functionName
const\s+functionName\s*=

# Python
def\s+function_name

# Go
func\s+FunctionName

Classes:

class\s+ClassName

Types/Interfaces:

(type|interface)\s+TypeName

Finding Usages

Imports:

import.*ComponentName
from\s+['"].*module['"]

Function Calls:

functionName\(

References:

\bvariableName\b

Finding Patterns

Error Handling:

catch\s*\(
\.catch\(
try\s*\{

API Endpoints:

(get|post|put|delete|patch)\s*\(
router\.(get|post)
@(Get|Post|Put)

Environment Variables:

process\.env\.
import\.meta\.env\.

Tools to Use

  • repo-search - Primary search tool with ripgrep
  • repo-map - Understand project structure first

Search Refinement

Too Many Results?

  1. Add file type filter: --type ts
  2. Add path glob: --glob "src/**"
  3. Make pattern more specific
  4. Use word boundaries: \bexact\b

Too Few Results?

  1. Remove filters
  2. Try case-insensitive: --ignoreCase
  3. Use broader pattern
  4. Check for typos
  5. Try alternative names/patterns

Common Glob Patterns

  • *.ts - All TypeScript files
  • src/**/*.ts - TypeScript in src
  • !**/node_modules/** - Exclude node_modules
  • **/*test* - Test files
  • **/components/** - Component files

Output Guidelines

Present Results Clearly

## Found: `handleAuth`

### Definition
📁 src/auth/handler.ts:42
export function handleAuth(request: Request) {

### Usages (5 found)
📁 src/routes/login.ts:15
  import { handleAuth } from '../auth/handler'

📁 src/routes/login.ts:28
  const result = await handleAuth(req)

📁 src/middleware/auth.ts:8
  import { handleAuth } from '../auth/handler'
...

Read the full file on GitHub · 155 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. 1mo ago First seen · 155 lines · 27 tokens per session scan A d2d6d67b8ae6

Subscribe to this mod's changes

search-code is a skill published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 800 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens