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/domain-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.00012 | $0.01563 |
| Opus 5 | $0.00006 | $0.00781 |
| Sonnet 5 | $0.00002 | $0.00313 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade A, and why
domain-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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Review
Scope: always Cites:
- domain-modeling
- ubiquitous-language
- adversarial-review-protocol
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status: pass=clean model, warn=minor issues, fail=boundary violations Severity: error=violation that causes data exposure, cross-context coupling, or untestable code; warning=misplaced logic or missing abstraction that adds friction; suggestion=modeling improvement with no immediate harm Confidence: high=mechanical (add missing DTO, rename to domain term); medium=direction clear, entity/service split may have tradeoffs; none=requires human judgment (aggregate boundary decisions, bounded context design)
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.
Knowledge Files
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/domain-modeling.md before starting analysis. Whole-file load: the agent uses every section — exploration patterns, anti-pattern recognition, ubiquitous-language drift detection, and the per-language ORM / boundary / application-service signals.
Explore
Follow the exploration patterns in ${CLAUDE_PLUGIN_ROOT}/knowledge/domain-modeling.md#exploration-patterns to
map the project structure: entity/model files, service layer,
repositories, DTOs, ORM markers, boundary entry points, and
application services.
If none of these patterns yield files, return skip.
Skip
Return {"status": "skip", "issues": [], "summary": "No domain model to analyze"} when:
- Target is infrastructure-only code (CI/CD, build scripts, configs)
- No business logic or domain entities 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 · 137 lines · 12 tokens per session scan A b9184d49dd02
domain-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,563 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.