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.
npx skills add JeremyDev87/codingbuddy --skill deepsearchgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/deepsearch)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/deepsearch"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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.
<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/deepsearch"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/deepsearch.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.00021 | $0.01734 |
| Opus 5.5 | $0.00008 | $0.00694 |
| Sonnet 5.5 | $0.00004 | $0.00347 |
| Haiku 4.5 | $0.00002 | $0.00173 |
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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Search
Overview
Single-pass searches miss connections. Grep finds strings, not understanding.
Core principle: ALWAYS search in multiple passes with increasing precision. A single query never gives the full picture.
Violating the letter of this process is violating the spirit of thorough search.
The Iron Law
NO CONCLUSIONS WITHOUT CROSS-REFERENCED EVIDENCE FROM MULTIPLE PASSES
If you haven't completed at least Phases 1-3, your understanding is incomplete.
When to Use
Use when simple grep/glob is insufficient:
- Understanding how a feature works end-to-end
- Tracing data flow across multiple files/modules
- Finding all usages and side effects before refactoring
- Detecting dead code or unused exports
- Mapping dependency chains
- Understanding implicit relationships (event emitters, dynamic imports, reflection)
- Auditing a pattern's usage across the codebase
Use this ESPECIALLY when:
- Initial search returns too many or too few results
- You need to understand "everything that touches X"
- The codebase uses indirection (dependency injection, plugins, event systems)
- You're about to make a breaking change
- You need confidence that nothing was missed
Don't use when:
- You know the exact file and symbol (use direct read)
- A single grep gives you the complete answer
- You're looking up a specific API signature
The Four Phases
You MUST complete each phase before drawing conclusions.
Phase 1: Broad Search — Cast a Wide Net
Goal: Discover all potentially relevant files and symbols.
-
Start with Multiple Search Strategies
- Search by name: function names, class names, variable names
- Search by pattern: string literals, error messages, log statements
- Search by structure: file naming conventions, directory patterns
- Search by type: imports, exports, type definitions
-
Use Varied Query Terms
- Don't stop at the first query term
- Try synonyms, abbreviations, related concepts
- Search for both the interface and the implementation
- Include test files — they reveal intended usage
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 · 215 lines · 21 tokens per session scan A f3983ab5649c
deepsearch is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 1,734 once invoked, about $0.0001 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.
Other skills, from other repositories
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…