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/component-architecture-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.00026 | $0.01456 |
| Opus 5 | $0.00013 | $0.00728 |
| Sonnet 5 | $0.00005 | $0.00291 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
component-architecture-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 3d 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.
Component Architecture Review
Scope: added-only
- **/*.jsx
- **/*.tsx
- **/*.vue
- **/*.svelte
- **/*.component.ts
- **/*.component.html Cites:
- frontend-component-architecture
- adversarial-review-protocol
Scope: newly-added frontend component files matching the globs above
(.jsx, .tsx, .vue, .svelte, Angular *.component.ts + their
templates) in /code-review's per-diff panel — merely modifying an
existing component file does not trigger this agent there (#1733):
whole-inventory duplication assessment is best judged against the entire
component set, which is exactly what /repo-review (#1735) runs this agent
against, unconditionally, every pass. Skip this agent entirely if the target
has no frontend component files.
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status: pass=components are well factored, warn=extraction or composition opportunities, fail=duplicated render/behavior forcing multi-site edits Severity: error=semantic UI duplication (a behavioral rule copied across components), warning=high-value extraction or prop-drilling fix, suggestion=composition/API-consistency cleanup Confidence: high=mechanical (extract the repeated subtree, call the existing primitive); medium=judgment call (is this duplication semantic or incidental? right granularity?); none=requires product knowledge (will these diverge?)
Context needs: full-file
Knowledge Files
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/frontend-component-architecture.md before analysis.
Whole-file load: it is a short reference catalog the agent scans end-to-end —
the detection categories, the rule-of-three / semantic-vs-incidental tests, and
the framework mapping are independent indexes used together on every review.
Skip
Return {"status": "skip", "issues": [], "summary": "No frontend component files in target"} when:
- No
.jsx,.tsx,.vue,.svelte, or component-rendering.js/.ts/Angular files exist in the target - All target files are backend, config, test, or documentation files
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.
- 3d ago First seen · 120 lines · 26 tokens per session scan A bd4249e12379
component-architecture-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,456 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.