file-search

file-search is a skill for Claude Code, Codex from markerikson/opencode-config-example. It costs 41 tokens per session (2,219 once invoked), scanned A, original, MIT.

A code-search guide using ripgrep for fast text searches and ast-grep for searches based on code structure.

In plain words
What is it for?
Use it to understand an unfamiliar project, find every use of a function before refactoring, locate API calls or error handling, and search for TODOs or suspicious code.
Why use it?
It makes it easier to find where code, functions, patterns, dependencies, security risks, and unfinished tasks appear across a codebase.

Skill for Claude CodeCodex

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

Good fit Use it to understand an unfamiliar project, find every use of a function before refactoring, locate API calls or error handling, and search for TODOs or suspicious code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markerikson/opencode-config-example/file-search
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 markerikson/opencode-config-example --skill file-search
Clone the repo
git clone --depth 1 https://github.com/markerikson/opencode-config-example

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/file-search"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/file-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,219 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.00041 $0.02219
Opus 5.5 $0.00016 $0.00888
Sonnet 5.5 $0.00008 $0.00444
Haiku 4.5 $0.00004 $0.00222

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

Security

Grade A, and why

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

config/skill/file-search/SKILL.md · 281 lines

How it starts

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

File Search Skill

Search code efficiently using ripgrep for text patterns and ast-grep for structural code patterns.

Purpose

The file-search skill provides access to two powerful search tools:

  1. ripgrep (rg): Ultra-fast text search with regex support for finding strings, patterns, and text matches
  2. ast-grep (sg): Syntax-aware structural search for finding code patterns based on abstract syntax trees

Use these tools to understand codebases, find usage patterns, analyze impact of changes, and locate specific code constructs. Both tools are significantly faster than traditional grep or find commands.

When to Use This Skill

Use the file-search skill when:

  • Understanding a new codebase (finding entry points, key classes)
  • Finding all usages of a function, class, or variable before refactoring
  • Locating specific code patterns (error handling, API calls, etc.)
  • Searching for security issues (hardcoded credentials, SQL queries, eval usage)
  • Analyzing dependencies and imports
  • Finding TODOs, FIXMEs, or code comments

Choose ripgrep for:

  • Text-based searches (strings, comments, variable names)
  • Fast, simple pattern matching across many files
  • When the exact code structure doesn't matter

Choose ast-grep for:

  • Structural code searches (function signatures, class definitions)
  • Syntax-aware matching (understanding code semantics)
  • Complex refactoring (finding specific code patterns)

Invoking Search Tools

Use the execute_command tool to run ripgrep and ast-grep:

# Using ripgrep
execute_command("rg 'pattern' --type py src/")

# Using ast-grep
execute_command("sg --pattern 'class $NAME { $$$ }' --lang python")

Both tools are pre-installed and available via shell execution.

Targeting Your Searches

CRITICAL: Always start with targeted, narrow searches to avoid overwhelming results. Getting thousands of matches makes analysis impossible and wastes tokens.

These strategies apply to both ripgrep and ast-grep.

Read the full file on GitHub · 281 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 · 281 lines · 41 tokens per session scan A fe1a622614d3

Subscribe to this mod's changes

file-search is a skill published in the GitHub repository markerikson/opencode-config-example (48 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 2,219 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens