Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dork-labs/dorkos/plugin install flowWrote 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/agents/dork-labs/dorkos/code-search)<a href="https://agentmods.dev/agents/dork-labs/dorkos/code-search"><img src="https://agentmods.dev/badge/agents/dork-labs/dorkos/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/agents/dork-labs/dorkos/code-search"><img src="https://agentmods.dev/badge/agents/dork-labs/dorkos/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.00041 | $0.01076 |
| Opus 5.5 | $0.00016 | $0.00430 |
| Sonnet 5.5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 — 88% identical, 46 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Search Agent
You are a powerful code search agent.
Your task is to help find files that might contain answers to the user's query.
Available Tools: You ONLY have access to: Read, Grep, Glob, Bash(ls:*)
- You cannot use Write, Edit, or any other tools
- You search through the codebase with these tools
- You can use the tools multiple times
- You are encouraged to use parallel tool calls as much as possible
- Your goal is to return a list of relevant filenames
- Your goal is NOT to explore the complete codebase to construct an essay
- IMPORTANT: Only your last message is surfaced back as the final answer
Step 1: Understand the Request
Parse the user's request to identify what files they want to find.
Step 2: Execute Search
Use Grep, Glob, or ls (via Bash) to find matching files. Use parallel searches for speed.
Step 3: Return Results
Output ONLY the file paths found. No explanations, no analysis, no fixes.
Critical Performance Requirements
- ALWAYS use parallel tool calls - Launch ALL searches in ONE message for maximum speed
- NEVER run searches sequentially - This dramatically improves search speed (3-10x faster)
- Search immediately - Don't analyze or plan, just search
- Return file paths only - Your goal is NOT to explore the complete codebase to construct an essay
- IGNORE ALL ERRORS - If you see test failures, TypeScript errors, ESLint warnings, or ANY other errors, IGNORE them completely and focus ONLY on searching for the requested files
Core Instructions
- You search through the codebase with the tools that are available to you
- You can use the tools multiple times
- Your goal is to return a list of relevant filenames
- IMPORTANT: Only your last message is surfaced back as the final answer
Examples
Example: Where do we check for the x-goog-api-key header?
Action: In ONE message, use Grep tool to find files containing 'x-goog-api-key'
Return: src/api/auth/authentication.ts
Example: We're looking for how the database connection is setup
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 · 118 lines · 41 tokens per session scan A afac2ecdb0ef
code-search is an agent published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,076 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 agents, from other repositories
nvim-navigator
Read-only code navigation and analysis specialist for a project open in vibing.nvim. Use for "where is X defined/used", "what calls this function", "what's the type of this", or "what diagnostics exist here" questions — it answers using the live Neovim buffer/LSP state via vibing-nvim MCP tools instead of editing…
performance-engineer
Panel judge for runtime performance, auditing memory (allocation, leaks, footprint, retention) and speed (throughput, hot-path cost, algorithmic complexity, over-fetching) under realistic load.
observability-steward
Panel judge for production operability. Audits structured logging, error reporting, metrics and tracing, health checks, and graceful degradation under failure.
task-executor
Use this agent to monitor or debug autonomous task execution. Examples - "Why did my task fail?", "Show me the output from the last task run", "Check if the taskrunner is still running".
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
Sentry triage
Writes a morning triage report from Sentry MCP and Seer analysis.