deepsearch

deepsearch is a skill for Claude Code from johnfkoo951/cmdspace-plugins. It costs 72 tokens per session (631 once invoked), scanned A, original, MIT.

A deep code-search skill that uses several ways to find relevant code, including text patterns, code structure, meaning, and Git history. Git is the version-control system commonly used to track a project's changes.

In plain words
What is it for?
Use it to find related code, discover where a feature is implemented, trace project history, or investigate how code is organized.
Why use it?
It can help locate code that a simple text search may miss, especially when you do not know the exact file, name, or wording to search for.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the dev-orchestrator plugin — 12 skills, 13 agents shipped together

Good fit Use it to find related code, discover where a feature is implemented, trace project history, or investigate how code is organized.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/johnfkoo951/cmdspace-plugins/deepsearch
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 johnfkoo951/cmdspace-plugins --skill deepsearch
Clone the repo
git clone --depth 1 https://github.com/johnfkoo951/cmdspace-plugins

Made for: Claude Code.

Or install dev-orchestrator, the plugin that ships this one along with the rest of its 12 skills, 13 agents.

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 deepsearch

README.md
[![agentmods](https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/deepsearch/github.svg)](https://agentmods.dev/skills/johnfkoo951/cmdspace-plugins/deepsearch)
Your own site
<a href="https://agentmods.dev/skills/johnfkoo951/cmdspace-plugins/deepsearch"><img src="https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/deepsearch/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 deepsearch

Your own site · 80×15
<a href="https://agentmods.dev/skills/johnfkoo951/cmdspace-plugins/deepsearch"><img src="https://agentmods.dev/badge/skills/johnfkoo951/cmdspace-plugins/deepsearch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 631 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.00072 $0.00631
Opus 5.5 $0.00029 $0.00252
Sonnet 5.5 $0.00014 $0.00126
Haiku 4.5 $0.00007 $0.00063

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

Security

Grade A, and why

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

plugins/dev-orchestrator/skills/deepsearch/SKILL.md · 85 lines

How it starts

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

Applies multiple search strategies to find code that simple text search misses.

Workflow

Step 1: Understand Search Intent

Use AskUserQuestion:

{
  "questions": [
    {
      "question": "What are you looking for?",
      "header": "Search Type",
      "options": [
        {"label": "Pattern/Usage", "description": "Find all places where a pattern is used (e.g., all async functions, all API calls)"},
        {"label": "Concept/Feature", "description": "Find code related to a concept (e.g., 'authentication', 'caching')"},
        {"label": "Changed code", "description": "Find code that was recently modified or relates to a specific change"},
        {"label": "Dead code", "description": "Find unused functions, imports, or variables"}
      ],
      "multiSelect": false
    }
  ]
}

Step 2: Apply Search Strategies

Dispatch explorer (Haiku) with instructions to apply multiple strategies in parallel:

Strategy 1: Textual Search

  • Use Grep with regex patterns
  • Search for exact names, patterns, and keywords

Strategy 2: Structural Search

  • Use Glob for file pattern matching
  • Trace import/export chains
  • Follow function call hierarchies

Strategy 3: Semantic Search

  • Search by concept (related terms, synonyms)
  • Look in comments, docstrings, variable names
  • Search for patterns that implement the concept

Strategy 4: Historical Search (if applicable)

  • Use git log --all -S "term" for code that appeared/disappeared
  • Use git log --follow for file history
  • Use git blame for authorship and timing

Step 3: Rank and Present Results

## Search Results: [Query]

### Strategy Results Summary
| Strategy | Matches | Top Result |
|----------|---------|------------|
| Textual | [N] | [file:line] |
| Structural | [N] | [file:line] |
| Semantic | [N] | [file:line] |
| Historical | [N] | [commit] |

### Top Results (by relevance)
1. **[file:line]** — [context snippet]
   - Found by: [strategy]
   - Relevance: [why this matches]

2. **[file:line]** — [context snippet]
   ...

### Related Files
- [Files that are connected to the search results]

Read the full file on GitHub · 85 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 · 85 lines · 72 tokens per session scan A 61badf32bda2

Subscribe to this mod's changes

deepsearch is a skill published in the GitHub repository johnfkoo951/cmdspace-plugins (7 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 631 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

gh-issue-triage

An automated workflow for handling issues in a project's GitHub repository, from collecting and analysing them through fixing, testing, and closing them.

Linearl/reasonix_skill_repo · 52 tokens

wiki-lint

Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason…

AgriciDaniel/claude-obsidian · 79 tokens

pr-reply

Answer reviewers on your own pull requests in other people's repos: find threads where the ball is on your side, tell humans from bots, do exactly what was asked and reply with evidence. Use at the start of any GitHub session or on a new-review alert. Triggers: /pr-reply, /prr, answer the reviewers, who is waiting on…

tonydzi/second-brain-starter-kit · 79 tokens

contrib-watch

Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.

tonydzi/second-brain-starter-kit · 54 tokens

github-growth

A working guide for promoting projects and starting useful conversations on GitHub. GitHub is a platform for hosting code, reviewing changes, and discussing software with its users and maintainers.

tonydzi/second-brain-starter-kit · 113 tokens

share-fix

Turn a fix you made for a whole class of bugs into help for others: reverse-search GitHub for people hitting the same symptom, pick the 3-5 best live threads and post one tailored answer or gist each, no copy-paste fan-out. Use after a verified class fix. Triggers: /share-fix, /sf, share the fix.

tonydzi/second-brain-starter-kit · 78 tokens