code-search
Read-only code search and investigation behind one stable tool surface. Finds code by meaning or structure, traces callers, callees and blast radius, and dispatches an analyze agent for deep dives. The search engine is named in project settings and is swappable.
| Version | 8.3.1 |
| Marketplace | magus |
| Commands | 3 |
| Subagents | 1 |
| Skills | 4 |
| MCP server | yes |
| Hooks | yes |
Install
magus
Find code-search on the Plugins tab and turn it on. magus registers the magus
marketplace if you do not have it, and installs what the plugin needs to actually run —
binaries, MCP servers, CLI tools.
For a team, press s to save your plugins as a profile and commit it. Everyone else runs
magus install — see Teams and profiles.
Prefer to do it by hand? Installing Magus has the manual path.
How to run these: understanding a codebase — what to type, what it asks you, and which options change the outcome.
When to reach for it
- Use when searching a codebase, locating a symbol, tracing callers, or about to open three or more files —
search
Commands
| Command | What it does |
|---|---|
/code-search:analyze | Investigate a codebase read-only — understand architecture, trace how a feature works, locate an implementation, or track a bug to its origin |
/code-search:help | Show what the code-search plugin provides — its agent, commands, skills, tool surface, and which one to reach for |
/code-search:setup | Set up code-search in this project: choose, install and configure a search engine, build its index, and verify. Asks before every change, and undoes an earlier ignore-for-this-project. |
Subagents
Dispatched with the Agent tool, each in its own context window.
| Agent | What it does |
|---|---|
code-search:analyze | | |
Skills
| How you get it | |
|---|---|
| ● | Claude can reach for it on its own |
| ○ | You invoke it by name |
Why a skill lands in one row or another
| Skill | What it covers | |
|---|---|---|
| ● | code-search:deep-analysis | Audits a codebase across seven dimensions, from architecture to code health, scoring each finding with evidence. |
| ● | code-search:investigate | Routes a code investigation to one of four modes — bug, test gap, architecture, implementation — and runs the query sequence that mode needs. |
| ● | code-search:search | Finds code by meaning, structure or exact text, then reads only the spans returned. Use when searching a codebase, locating a symbol, tracing callers, or about to open three or more files. |
| ○ | code-search:setup | Sets up code-search in a project (search engine, index and settings) through its setup CLI, asking before every change. |
MCP server
This plugin runs an MCP server; its tools appear as mcp__* once the plugin is enabled.
Hooks
This plugin installs hooks. They run automatically and are the usual first place to look if its behaviour stops firing.
Source
plugins/code-search/ on GitHub, including its full README.