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/anilcancakir/claude-code-plugins/serena-navigatornpx skills add anilcancakir/claude-code-plugins --skill serena-navigatorgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/serena-navigator)<a href="https://agentmods.dev/skills/anilcancakir/claude-code-plugins/serena-navigator"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugins/serena-navigator.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.00069 | $0.00404 |
| Opus 5 | $0.00034 | $0.00202 |
| Sonnet 5 | $0.00014 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
serena-navigator 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 6d 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.
What it actually says
Serena Semantic Navigation
Token-Efficient Reading Pattern
Instead of reading entire files:
- Get overview first:
get_symbols_overview(file)- See all functions/classes - Locate specific symbol:
find_symbol(name)- Get exact location - Read targeted section:
read_file(path, start_line, end_line)- Only what's needed
This pattern saves 90%+ tokens on large files.
Tool Selection Guide
| Task | Tool |
|---|---|
| See file structure | get_symbols_overview(file_path) |
| Find definition | find_symbol(name) |
| Find all usages | find_referencing_symbols(symbol_name) |
| Search text/comments | search_for_pattern(pattern) |
Example Workflow: Understanding Code
1. get_symbols_overview("src/services/payment.py")
→ See PaymentProcessor class with all methods
2. find_symbol("process_payment")
→ Get exact location and signature
3. find_referencing_symbols("process_payment")
→ Find all call sites
4. read_file("src/services/payment.py", start_line=45, end_line=80)
→ Read only the relevant method
When to Use Text Search
Use search_for_pattern for:
- String literals and comments
- Configuration values
- Non-code patterns
Memory Integration
Check existing project knowledge:
list_memories()
read_memory("architecture_overview")
Save discoveries:
write_memory(key="architecture_overview", content="...")
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.
- 6d ago First seen · 66 lines · 69 tokens per session scan A 84a4fb314edb
serena-navigator is a skill published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 7mo ago), licensed MIT. It adds 69 tokens to every session and 404 once invoked, about $0.0003 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
debugger
Systematic debugging method: 5-step root-cause analysis (capture, isolate, hypothesize, investigate, fix & verify) plus common bug-pattern reference. Use when errors, exceptions, test failures, or unexpected behavior appear. Loaded automatically by the debugger agent.
mcp-check
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
project-health-check
Audit project health across 7 dimensions (documentation, test coverage, security, code quality, dependencies, database, build/deploy) producing a scored report with prioritized fixes. Use for periodic checkups, before releases, or when the user runs /project-health-check.
doctor
Diagnose Cladding runtime health — Claude Code hook liveness and version, CI package pinning, lifecycle governance, and sentinel-miss frequency by phase × cause × fallback. Use when hooks may be silent, CI may float across Cladding releases, scan or run results look thinner than expected, or before tuning the host…
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…