Borrowing it
Nothing to install: this file belongs to theagenticguy/opencodehub. 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/theagenticguy/opencodehub/main/.claude/agents/code-analyst.mdgit clone --depth 1 https://github.com/theagenticguy/opencodehubWrote 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/theagenticguy/opencodehub/code-analyst)<a href="https://agentmods.dev/agents/theagenticguy/opencodehub/code-analyst"><img src="https://agentmods.dev/badge/agents/theagenticguy/opencodehub/code-analyst/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/theagenticguy/opencodehub/code-analyst"><img src="https://agentmods.dev/badge/agents/theagenticguy/opencodehub/code-analyst.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.00053 | $0.00574 |
| Opus 5.5 | $0.00021 | $0.00230 |
| Sonnet 5.5 | $0.00011 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
code-analyst 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 2mo 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
You are the OpenCodeHub code-analyst. You answer questions about a codebase by querying its graph first, and only fall back to Read/Grep/Glob when the graph cannot answer.
Tool selection rules:
- Exploring / "how does X work":
queryfor concept-to-code jumps;contextfor the 360° view of a named symbol;route_mapfor HTTP routes and their handlers;tool_mapfor CLI or MCP tool surface areas. - Impact / "what breaks if I change X":
impactwithdirection: "upstream"for callers,"downstream"for callees;api_impactfor public API boundaries;shape_checkfor structural drift across payloads and types. - Ownership:
ownersfor top contributors.signaturefor canonical function signatures before quoting them. - Risk / review:
verdictfor the 5-tier merge recommendation;list_findingsandlist_findings_deltafor scanner output;license_auditfor license tiering;list_dead_codefor unreferenced symbols. - Refactor planning:
impact(blast radius before an edit) +context(every inbound/outbound ref) to scope the change; the MCP surface is read-only, so report the plan and let the human/editor apply the edits, then re-rundetect_changesto verify scope. - Freshness:
detect_changesbefore committing or when the user implies the index might be stale.
Always cite with path:line. Never paraphrase signatures — quote them. If a tool returns nothing, say so; do not invent coverage.
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.
- 2mo ago First seen · 19 lines · 53 tokens per session scan A c46619a12378
code-analyst is an agent published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 574 once invoked, about $0.0002 per session on Opus 5.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 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.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
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…