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 husnainpk/SymDex --skill symdex-code-searchgit clone --depth 1 https://github.com/husnainpk/SymDexWrote 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/husnainpk/symdex/symdex-code-search)<a href="https://agentmods.dev/skills/husnainpk/symdex/symdex-code-search"><img src="https://agentmods.dev/badge/skills/husnainpk/symdex/symdex-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/skills/husnainpk/symdex/symdex-code-search"><img src="https://agentmods.dev/badge/skills/husnainpk/symdex/symdex-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.00085 | $0.02113 |
| Opus 5 | $0.00043 | $0.01056 |
| Sonnet 5 | $0.00017 | $0.00423 |
| Haiku 4.5 | $0.00009 | $0.00211 |
Grade A, and why
symdex-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 9d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SymDex Code Search
Use SymDex before broad file browsing. Use it to save tokens by retrieving the exact code the agent needs instead of scanning whole files. SymDex currently covers 21 language surfaces, including Python, Go, Kotlin, Dart, Swift, HTML, CSS, Shell, Vue/Svelte script blocks, and Markdown headings plus supported fenced code blocks.
Current SymDex Snapshot
- Package version:
0.1.26 - Latest public tag:
v0.1.26 - MCP tool surface: 21 tools
- Language coverage: 21 language surfaces, including Android/Kotlin, Flutter/Dart, iOS/Swift, HTML, CSS-family stylesheets, Shell, Vue/Svelte script blocks, Markdown headings, and supported fenced code blocks
- Route extraction: Python, JavaScript/TypeScript, Spring/Kotlin, Laravel, Gin-style Go, ASP.NET, Rails/Sinatra, Phoenix, and Actix
- Search outputs: one-line CLI token-savings footers plus MCP
roi,roi_summary, androi_agent_hint - Quality outputs: MCP results and CLI JSON include
qualitywith confidence, freshness, parser mode, language surface, generated-file hints, and embedding availability - Context packs: CLI
symdex packand MCPbuild_context_packassemble token-budgeted evidence bundles for broader feature questions - Semantic backends: local
sentence-transformers, Voyage, OpenAI-compatible/embeddings, Gemini, and compatible proxies - Hosted embedding support:
SYMDEX_EMBED_RPMplussymdex index --lazyfor foreground structural indexing with background embedding fill - No-embedding mode:
symdex index --no-embedskips semantic embedding work entirely - Watch behavior: low-memory structural refresh by default; use
symdex watch --embedonly when semantic embeddings must refresh continuously - State model: global
~/.symdexby default, optional workspace-local./.symdexwithregistry.json - Markdown support:
.md,.markdown, and.mdxheadings plus supported fenced code blocks are indexed alongside source files
Start Here
- If the SymDex CLI reports a newer release, prefer upgrading before long sessions.
- Confirm the repo id.
- If the repo id is already known, pass
repoon every scoped tool call. - If the repo id is unknown, call
list_reposand match the current worktree. - Check freshness with
get_index_status(repo). - If the current worktree is not indexed, call
index_folder(path="."). - If the workspace already has
.symdex, treat it as the intended local SymDex state and reuse it. - Reuse the returned
repoid for the rest of the task.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 163 lines · 85 tokens per session scan A caa998587fa5
symdex-code-search is a skill published in the GitHub repository husnainpk/SymDex (209 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 2,113 once invoked, about $0.0004 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.