# Code Search

> Find where something lives in an unfamiliar Workspace. Use when asked where a function, symbol, config value, or piece of behaviour is defined, or when you need to understand a codebase's layout before changing it.

- **Type:** Skill
- **Install:** `agentstack add skill-1aifanatic-super-computer-code-search`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [1aifanatic](https://agentstack.voostack.com/s/1aifanatic)
- **Installs:** 0
- **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [1aifanatic](https://github.com/1aifanatic)
- **Source:** https://github.com/1aifanatic/super-computer/tree/main/skills/code-search

## Install

```sh
agentstack add skill-1aifanatic-super-computer-code-search
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Finding things in a Workspace

Search before you read. Reading whole files to locate one symbol wastes context you will need later for the actual work.

## Order of operations

1. `list_dir /workspace` first. Layout tells you where to look and stops you searching the whole tree.
2. `glob` when you know roughly what the file is called — `*.config.*`, `*test*`, `*.md`.
3. `grep` when you know what the code *says* rather than where it lives.
4. `read_file` last, and with `offset`/`limit` once grep has told you the line number.

## Patterns that pay off

Find a definition rather than every mention:

```
grep -rn "function handlePayment" /workspace
grep -rn "class .*Repository" /workspace
grep -rn "export (const|function|class) name" /workspace
```

Find callers, then narrow:

```
grep -rn "handlePayment(" /workspace
```

Find configuration and constants:

```
grep -rni "timeout|retry|max_|limit" /workspace
```

Get the shape of a file cheaply before reading it:

```
grep -n "^(export |function |class |def |const )" /workspace/src/thing.ts
```

## When a search returns too much

Do not read all of it. Narrow instead: add a directory, add context to the pattern, or count first with `grep -rc pattern /workspace` to see whether the search was even the right one.

## Reporting

Answer with file paths and line numbers, not prose summaries of code the Operator can read. `src/billing.ts:412` is more useful than three sentences describing what happens there.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [1aifanatic](https://github.com/1aifanatic)
- **Source:** [1aifanatic/super-computer](https://github.com/1aifanatic/super-computer)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-1aifanatic-super-computer-code-search
- Seller: https://agentstack.voostack.com/s/1aifanatic
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.