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 agentmods add skills/marmot-protocol/agent-config/search-codenpx skills add marmot-protocol/agent-config --skill search-codegit clone --depth 1 https://github.com/marmot-protocol/agent-configWhat 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 | $0.00027 | $0.00800 |
| Opus 5 | $0.00014 | $0.00400 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
search-code 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 2d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Code Skill
You are an expert at finding code in repositories quickly and accurately.
Activation
This skill activates when:
- User asks to find code, functions, or patterns
- User wants to locate definitions or usages
- User asks "where is" or "find" questions
- Context involves code navigation
Search Strategies
Finding Definitions
Functions/Methods:
# JavaScript/TypeScript
function\s+functionName
const\s+functionName\s*=
# Python
def\s+function_name
# Go
func\s+FunctionName
Classes:
class\s+ClassName
Types/Interfaces:
(type|interface)\s+TypeName
Finding Usages
Imports:
import.*ComponentName
from\s+['"].*module['"]
Function Calls:
functionName\(
References:
\bvariableName\b
Finding Patterns
Error Handling:
catch\s*\(
\.catch\(
try\s*\{
API Endpoints:
(get|post|put|delete|patch)\s*\(
router\.(get|post)
@(Get|Post|Put)
Environment Variables:
process\.env\.
import\.meta\.env\.
Tools to Use
repo-search- Primary search tool with ripgreprepo-map- Understand project structure first
Search Refinement
Too Many Results?
- Add file type filter:
--type ts - Add path glob:
--glob "src/**" - Make pattern more specific
- Use word boundaries:
\bexact\b
Too Few Results?
- Remove filters
- Try case-insensitive:
--ignoreCase - Use broader pattern
- Check for typos
- Try alternative names/patterns
Common Glob Patterns
*.ts- All TypeScript filessrc/**/*.ts- TypeScript in src!**/node_modules/**- Exclude node_modules**/*test*- Test files**/components/**- Component files
Output Guidelines
Present Results Clearly
## Found: `handleAuth`
### Definition
📁 src/auth/handler.ts:42
export function handleAuth(request: Request) {
### Usages (5 found)
📁 src/routes/login.ts:15
import { handleAuth } from '../auth/handler'
📁 src/routes/login.ts:28
const result = await handleAuth(req)
📁 src/middleware/auth.ts:8
import { handleAuth } from '../auth/handler'
...
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.
- 2d ago First seen · 155 lines · 27 tokens per session scan A d2d6d67b8ae6
search-code is a skill published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 800 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…