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 skills/bdfinst/agentic-dev-team/frontend-architecturenpx skills add bdfinst/agentic-dev-team --skill frontend-architecturegit 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/skills/bdfinst/agentic-dev-team/frontend-architecture)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/frontend-architecture"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/frontend-architecture.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.00106 | $0.01244 |
| Opus 5 | $0.00053 | $0.00622 |
| Sonnet 5 | $0.00021 | $0.00249 |
| Haiku 4.5 | $0.00011 | $0.00124 |
Grade A, and why
frontend-architecture 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architecture
Role: orchestrator. This command scopes the changeset to frontend component
files and dispatches the component-architecture-review agent, then aggregates
one report. It does not review files itself — it coordinates.
/code-review dispatches the same agent automatically, but only when a
frontend component file is newly added (Scope: added-only, #1733) —
merely modifying an existing one does not trigger it there. This command
scopes the agent to the frontend files you name (--path/--since/--all),
regardless of whether any are newly added — use it for a diff that only
modifies existing components, a standalone frontend-only pass (e.g. before
extracting a component library), or to scope beyond a diff. /repo-review
(#1735) covers the third, unconditional case: the whole component inventory,
every pass, with no scoping flags at all.
This command is executed under orchestrator direction. Dispatch the agent with
its model:/effort: frontmatter as declared — the harness resolves both
fields natively before dispatch, per Model/Effort Resolution in
agents/orchestrator.md (ADR 0026).
Orchestrator constraints
- Advisory only. Aggregate findings and recommendations. Do not edit
component code. Hand actionable fixes to
/apply-fixesor/build. - Scope to the frontend. Only pass frontend component files to the agent; skip the run with a one-line note if none are in scope.
- No double-reporting. This review owns component reuse and composition.
Defer accessibility to
a11y-review, framework reactivity to the framework-reactivity reviewers (react-reactivity-review/vue-reactivity-review/angular-reactivity-review), non-UI logic duplication and SRP/coupling tostructure-review/refactor-opportunity-review, and naming tonaming-review. When the same line belongs to one of those, drop it here. - Be concise. One aggregated report. Issue messages one sentence; recommendations map to a concrete next edit (extract X, lift Y to context).
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 · 114 lines · 106 tokens per session scan A 3c8f38a98580
frontend-architecture is a skill published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 1,244 once invoked, about $0.0005 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-03.
Other skills, from other repositories
qt-qml-review
Invoke when the user asks to review, check, audit, or look over Qt6 QML code -- or suggest before committing. Runs deterministic linting (47+ rules) then six parallel deep- analysis agents covering bindings, layout, loaders, delegates, states, and performance. Optionally invokes system qmllint for type-level checks.…
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence. Do not use for generic code review, PR review…
review-persistence-security-resources
Normative reviewer for persistence, settings, secrets, logging hygiene, resources, caches, cross-platform behavior and long-lived state in the explyt/spring-plugin IntelliJ plugin. Use when reviewing changes that touch PersistentStateComponent, settings UI, credentials, caches, service fields, logging, file paths…
tool-ast-grep-rules
Write AST-based code search and rewrite rules using ast-grep YAML. Create linting rules, code modernizations, and API migrations with auto-fix. Use when the user mentions ast-grep, tree-sitter patterns, code search rules, lint rules with YAML, AST matching, or code refactoring patterns.