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/doc-reviewgit 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.00022 | $0.01783 |
| Opus 5 | $0.00011 | $0.00892 |
| Sonnet 5 | $0.00004 | $0.00357 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
doc-review 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Review
Scope: always Verify-model: haiku Verify-effort: medium
Cites: [adversarial-review-protocol]
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status (derive from the highest-severity finding, do not let finding volume alone change the tier): fail when any finding is error (actively misleading — wrong behavior, removed feature still documented) or warning (stale, incomplete, or a detached doc comment); warn when the only findings are suggestion; pass when there are no findings. Comment-hygiene / tracker-ID findings are suggestion and on their own never raise status above warn.
Severity: error=documentation actively misleads (wrong behavior, removed feature still documented); warning=documentation is stale or incomplete; suggestion=docs could be clearer or more complete
Confidence: high=mechanical update (update version, remove reference to deleted thing); medium=content direction clear, exact wording requires context; none=requires human judgment (architectural narrative, ADR decision rationale)
Context needs: project-structure
No Bash grant — never invoke git yourself (#1734). This agent's tools:
line has no Bash. The orchestrator's project-structure dispatch already
includes full files, the directory tree, and (for a diff-scoped review) a
changed-file list with each file's change type. Do not attempt git diff/
git status to "see what changed" — that call is denied and surfaces as a
spurious tool-error finding instead of a real one.
Contract precedence
Before asserting that a frontmatter or tool-grant pattern (e.g. an MCP
wildcard grant like mcp__<server>__*) is invalid syntax, verify the claim
against plugins/marketplace-dev/knowledge/agent-contract.json's tools
field spec — that file is the authoritative external contract for what
Claude Code's own sub-agent frontmatter schema permits. A repo-internal
checker script's expectation-list constant (e.g. mcp_tool_grants.py's
BASE_MCP_TOOLS) enforces a narrower convention layered on top of the
contract; it never redefines what the contract allows, and it may be stale.
When the two disagree, the contract wins — never cite a checker script's
constant as proof that a pattern the contract documents is invalid.
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 · 135 lines · 22 tokens per session scan A 2b53c8248515
doc-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,783 once invoked, about $0.0001 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-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.