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 agents/bdfinst/agentic-dev-team/codebase-recongit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWhat 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 | $0.00060 | $0.03004 |
| Opus 5 | $0.00030 | $0.01502 |
| Sonnet 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 2d 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.
- 2d 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 (277 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 3,004 once invoked, about $0.0003 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.