Borrowing it
Nothing to install: this file belongs to achreftlili/code-index. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/achreftlili/code-index/main/.claude/skills/code-search/SKILL.mdgit clone --depth 1 https://github.com/achreftlili/code-indexWrote 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.
[](https://agentmods.dev/skills/achreftlili/code-index/code-search)<a href="https://agentmods.dev/skills/achreftlili/code-index/code-search"><img src="https://agentmods.dev/badge/skills/achreftlili/code-index/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.
<a href="https://agentmods.dev/skills/achreftlili/code-index/code-search"><img src="https://agentmods.dev/badge/skills/achreftlili/code-index/code-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.00663 |
| Opus 5.5 | $0.00022 | $0.00265 |
| Sonnet 5.5 | $0.00011 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00066 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-search — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-search
You have access to a pre-built code index over this repo, exposed as MCP tools.
Default to the index for navigation. Only Read after you know the exact path
and line range.
Routing decision tree
| You have... | Use first |
|---|---|
| An identifier (camelCase, snake_case, ALL_CAPS) | symbol_lookup |
| A concept ("auth flow", "parsing markdown") | code_search |
| A file path and want its structure | file_outline |
| A symbol_id and want full code | get_symbol_body |
| "What calls this?" | callers |
| "What does this depend on?" | callees |
| "Who imports this file?" | dependents |
| "What does this file import?" | dependencies |
Composition recipes
Trace a feature end-to-end
code_search "<feature concept>"→ top hits.- For the most promising hit,
callersto find entry points. - For each entry point,
calleesto map the call graph. get_symbol_bodyonly on the symbols you actually need to understand.
Plan a refactor / assess blast radius
symbol_lookupthe function/class.callers symbol_id depth=2for transitive impact.dependents pathfor files importing the module.
Onboard to a new module
dependencies path→ upstream modules the file leans on.file_outline path→ structure.code_searchonly if you need a particular concept.
Anti-patterns
- Don't
Readbefore searching. Reading a 500-line file to find one symbol costs ~10x the tokens ofsymbol_lookup+get_symbol_body. - Don't
Grepfor an identifier. Grep returns raw lines;symbol_lookupreturns the symbol with its signature, file, and line range. - Don't read more than ~50 lines of a found chunk. If the snippet is too
trimmed, call
get_symbol_bodyinstead of expanding the read. - Don't ask the index to refresh itself. A
PostToolUsehook reindexes onEdit/Write/MultiEdit. The watcher catches IDE-side edits.
Staleness recovery
If a result's line numbers don't match the file you then Read (e.g. you
checked out a new branch), retry the same call once — file_outline and
get_symbol_body reindex the file synchronously when they detect a stale
mtime. If two retries disagree with the file, fall back to Grep once and
report the inconsistency.
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.
- 1mo ago First seen · 64 lines · 56 tokens per session scan A 0713133cb3c5
code-search is a skill published in the GitHub repository achreftlili/code-index (1 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 663 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-31.
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…
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.
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…
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…
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.
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…