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.
git clone --depth 1 https://github.com/bdfinst/agentic-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/deep-code-reasoning)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/deep-code-reasoning"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/deep-code-reasoning.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.00045 | $0.01095 |
| Opus 5 | $0.00023 | $0.00548 |
| Sonnet 5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
deep-code-reasoning 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 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.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Code Reasoning
Phase 1b peer agent. Catches vulnerabilities that require cross-file reasoning — IDOR, confused deputy, TOCTOU, indirect privilege escalation, workflow bypass. Scope discipline is mandatory: read only RECON- identified surface.
Context needs: project-structure
Inputs
memory/recon-<slug>.json—entry_points,security_surface.auth_paths,security_surface.sensitive_data_flows(required)- Target repo files at RECON-identified paths (on demand; load scoped files + immediate callers/callees only)
Output
memory/deep-reasoning-<slug>.json— JSON array of unified findings. Schema:plugins/dev-team/knowledge/schemas/unified-finding-v1.json.
Required metadata: source: "llm-reasoning", cwe[] (≥ 1),
confidence (high|medium only — never low), secondary_locations[]
(≥ 1), reasoning (2-3 sentences tracing the attack path).
Scope extraction
Read memory/recon-<slug>.json:
entry_points[]— HTTP handlers, CLI, cron, event consumerssecurity_surface.auth_paths[]security_surface.sensitive_data_flows[]
If security_surface is missing, grep for common auth indicators
(@require_auth, hasPermission, isAuthorized, checkRole,
verify_token, @login_required, [Authorize]) and use the matching
files as the working surface. Document the fallback in the first entry's
metadata.
Detection categories (rule_id prefixes)
llm-reasoning.idor.<descriptor>— object-level authorization bypassllm-reasoning.function-level-authz.<descriptor>— function-level auth gapllm-reasoning.confused-deputy.<descriptor>— confused deputy / SSRF via delegationllm-reasoning.toctou.<descriptor>— time-of-check-time-of-usellm-reasoning.privilege-escalation.<descriptor>— indirect privilege escalationllm-reasoning.workflow-bypass.<descriptor>— business logic / state machine bypass
OWASP cross-reference: broken access control (A01:2021), confused deputy, TOCTOU across service boundaries, indirect privilege escalation, business logic bypass.
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 · 120 lines · 45 tokens per session scan A 4ff201e9bacd
deep-code-reasoning is an agent published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 1,095 once invoked, about $0.0002 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-09-05.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.