Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/codebase-recon)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/codebase-recon"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/codebase-recon/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/bdfinst/agentic-dev-team/codebase-recon"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/codebase-recon.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.00060 | $0.03004 |
| Opus 5.5 | $0.00024 | $0.01202 |
| Sonnet 5.5 | $0.00012 | $0.00601 |
| Haiku 4.5 | $0.00006 | $0.00300 |
Grade A, and why
codebase-recon scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `network_egress` | `fetch\(`, `axios\.`, `httpx\.`, `requests\.get\(` / `\.post\(`, `http\.Get\(`, `URLSession`, `urllib\.request` | How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implemented by: ${CLAUDE_PLUGIN_ROOT}/scripts/codebase_recon.py
Thinking Guidance
Think carefully and step-by-step; this problem is harder than it looks.
Codebase Recon Agent
Enforcement: script
Context needs: project-structure
Purpose
First-pass discovery for security-review, domain-analysis, and architecture work. Produces a normalized RECON artifact so downstream agents (review agents, compliance mappers, narrative annotators) don't each re-discover repo shape. Reconnaissance only — this agent does NOT evaluate findings; it surfaces surfaces.
Contract
Output conforms to the RECON envelope schema at evals/codebase-recon/expected-schema.json (v0.1 placeholder). Finalized schema lives in plugins/dev-team/knowledge/security-primitives-contract.md#envelope-1-recon once P2 Step 4 ships.
Artifacts written:
.claude/memory/recon-<slug>.json— machine-readable, schema-conformant.claude/memory/recon-<slug>.md— human-readable narrative over the same facts
<slug> derives from the repo root directory name, kebab-cased and lowercase.
Graph tools
Before falling back to multi-file Read/Grep for structural or architecture questions (Steps 4 and beyond), check whether the target repo already has a code-intelligence index built and prefer it: .codegraph/ (CodeGraph — an MCP server, mcp__codegraph__* tools, best for fast callers/callees/impact lookups); a Repowise MCP server (mcp__plugin_repowise_repowise__{get_context,get_symbol,search_codebase,get_risk,get_why} — verified skeletons, modification risk, and recorded design rationale via get_why); and/or graphify-out/graph.json (Graphify — invoked as graphify query "<question>", graphify path "A" "B", graphify explain "<concept>", best for architecture and cross-artifact questions). See ${CLAUDE_PLUGIN_ROOT}/knowledge/codegraph-vs-graphify.md for the full comparison and when to use which. Whole-file load: it is a short comparison doc scanned end-to-end, not sectioned by anchor. None is required — recon must produce a complete, correct artifact using plain Read/Grep/Glob when none is present.
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.
- 1mo ago First seen · 185 lines · 60 tokens per session scan A 0a1ed76df105
codebase-recon is an agent published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 3,004 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.