search-code

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

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.

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

Made for: Claude Code, Codex.

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. 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 $0.00027 $0.00800
Opus 5 $0.00014 $0.00400
Sonnet 5 $0.00005 $0.00160
Haiku 4.5 $0.00003 $0.00080

Measured 2d ago against content hash d2d6d67b8ae6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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. 2d 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 7mo ago), licensed MIT. It adds 27 tokens to every session and 800 once invoked, about $0.0001 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-31.

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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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