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/jmylchreest/aide/code-searchnpx skills add jmylchreest/aide --skill code-searchgit clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/code-search)<a href="https://agentmods.dev/skills/jmylchreest/aide/code-search"><img src="https://agentmods.dev/badge/skills/jmylchreest/aide/code-search.svg" alt="Measured on agentmods" 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.00015 | $0.01087 |
| Opus 5 | $0.00008 | $0.00544 |
| Sonnet 5 | $0.00003 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00109 |
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 5d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Search
Recommended model tier: balanced (sonnet) - this skill performs straightforward operations
Search for code symbols (functions, classes, methods, types) and find their call sites.
Available Tools
1. Search Symbols (mcp__plugin_aide_aide__code_search)
Find functions, classes, methods, interfaces, and types by name or signature.
Example usage:
Search for: "getUserById"
→ Uses code_search tool
→ Returns: function signatures, file locations, line numbers
2. Find References (mcp__plugin_aide_aide__code_references)
Find all places where a symbol is called/used.
Example usage:
Who calls "getUserById"?
→ Uses code_references tool
→ Returns: all call sites with file:line and context
3. List File Symbols (mcp__plugin_aide_aide__code_symbols)
List all symbols defined in a specific file.
Example usage:
What functions are in src/auth.ts?
→ Uses code_symbols tool
→ Returns: all functions, classes, types in that file
4. File Outline (mcp__plugin_aide_aide__code_outline)
Get a collapsed structural outline of a file — signatures preserved, bodies replaced with { ... }.
Uses ~5-15% of the tokens of the full file. Use this before reading a file to understand its
structure, then use Read with offset/limit for specific sections.
Example usage:
Outline src/auth.ts
→ Uses code_outline tool
→ Returns: collapsed view with signatures, line ranges, bodies collapsed
5. Check Index Status (mcp__plugin_aide_aide__code_stats)
Check if the codebase has been indexed.
Example usage:
Is the code indexed?
→ Uses code_stats tool
→ Returns: file count, symbol count, reference count
6. Search Findings (mcp__plugin_aide_aide__findings_search)
Search static analysis findings (complexity hotspots, secrets, code clones, coupling issues).
Example usage:
Any complexity issues in src/auth?
→ Uses findings_search tool with query "auth" or file filter
→ Returns: findings with file, line, severity, description
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.
- 5d ago First seen · 157 lines · 15 tokens per session scan A 4f1ac607181e
code-search is a skill published in the GitHub repository jmylchreest/aide (16 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,087 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-30.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.