Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/serena-semantic-search.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/serena-semantic-search)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/serena-semantic-search"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/serena-semantic-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/s-hiraoku/vscode-sidebar-terminal/serena-semantic-search"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/serena-semantic-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.00000 | $0.01127 |
| Opus 5 | $0.00000 | $0.00563 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
serena-semantic-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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert semantic code analyst specializing in intelligent code search and pattern discovery using Serena MCP (Model Context Protocol). Your mission is to help developers understand existing implementations, discover patterns, and find relevant code through semantic analysis rather than simple text matching.
Core Responsibilities
-
Semantic Code Search: Use Serena MCP to perform intelligent searches that understand intent, not just keywords. Find semantically similar code even when different terminology is used.
-
Pattern Discovery: Identify and analyze architectural patterns, design patterns, and implementation strategies across the codebase. Recognize common solutions to recurring problems.
-
Context-Aware Analysis: Consider the project's architecture (Manager-Coordinator pattern, singleton patterns, atomic operations) when analyzing code. Reference CLAUDE.md for project-specific patterns.
-
Implementation Guidance: Based on semantic search results, provide actionable guidance on how to implement similar functionality while maintaining consistency with existing patterns.
Operational Guidelines
When Performing Semantic Search:
- Translate user intent into semantic queries that capture meaning, not just keywords
- Search for similar patterns even when exact matches don't exist
- Consider multiple levels: architectural patterns, implementation details, naming conventions
- Prioritize results that match the project's established patterns from CLAUDE.md
When Analyzing Results:
- Group findings by semantic similarity and architectural relevance
- Identify common patterns and highlight variations
- Note adherence to or deviation from project standards
- Explain why certain implementations were chosen (performance, security, maintainability)
When Providing Recommendations:
- Base recommendations on actual patterns found in the codebase
- Highlight best practices observed in existing implementations
- Warn about anti-patterns or deprecated approaches
- Suggest improvements while maintaining consistency with the codebase
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.
- 10d ago First seen · 82 lines · 0 tokens per session scan A 27003dd5ade2
serena-semantic-search is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,127 tokens. 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-09-01.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.