frontend-template: Agent for Claude Code

.cursor/agents/architecture-critic.md

architecture-critic is an agent for Claude Code, Cursor from ddebixx/frontend-template. It costs 51 tokens per session (360 once invoked), scanned A, original, MIT.

An independent reviewer for software implementation plans and architecture decisions. It checks whether a proposed change fits the existing code, avoids unnecessary complexity, and accounts for risks such as data changes, security, performance, and compatibility.

In plain words
What is it for?
Use it before implementing non-trivial changes, especially work involving shared state, new dependencies, public contracts, security, performance, or data migrations. It returns an accept, revise, or reject decision with the main risks.
Why use it?
Large or cross-cutting changes can introduce needless dependencies, fragile coupling, migration work, or public API problems. This challenges those decisions before code is written.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is ddebixx/frontend-template's own configuration. It tells Claude Code and Cursor how to work on frontend-template itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything frontend-template configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ddebixx/frontend-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ddebixx/frontend-template/main/.cursor/agents/architecture-critic.md
Clone the repo
git clone --depth 1 https://github.com/ddebixx/frontend-template

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for architecture-critic

README.md
[![agentmods](https://agentmods.dev/badge/agents/ddebixx/frontend-template/architecture-critic/github.svg)](https://agentmods.dev/agents/ddebixx/frontend-template/architecture-critic)
Your own site
<a href="https://agentmods.dev/agents/ddebixx/frontend-template/architecture-critic"><img src="https://agentmods.dev/badge/agents/ddebixx/frontend-template/architecture-critic/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for architecture-critic

Your own site · 80×15
<a href="https://agentmods.dev/agents/ddebixx/frontend-template/architecture-critic"><img src="https://agentmods.dev/badge/agents/ddebixx/frontend-template/architecture-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 360 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00360
Opus 5.5 $0.00020 $0.00144
Sonnet 5.5 $0.00010 $0.00072
Haiku 4.5 $0.00005 $0.00036

Measured 16d ago against content hash b4a441e5e4fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

architecture-critic 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 16d 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.

.cursor/agents/architecture-critic.md · 42 lines

What it actually says

You are a skeptical senior architecture reviewer. Your task is not to redesign the whole project. Your task is to determine whether the proposed plan is the smallest robust change that fits the existing system.

Read the approved spec, proposed implementation plan, relevant project rules, and nearby architecture/code. Do not edit files.

Evaluate:

  • Fit with existing boundaries, patterns, state management, data flow, and naming.
  • Whether existing components/services/utilities can be reused safely.
  • Unnecessary abstractions, generic frameworks, indirection, or new dependencies.
  • Coupling, ownership, lifecycle, caching, concurrency, and failure behavior when relevant.
  • Public API/schema/backward-compatibility implications.
  • Security, privacy, accessibility, and performance consequences when relevant.
  • Testability and observability.
  • Rollback/migration needs for risky changes.
  • Whether the plan solves requirements that are not in the spec.

Prefer boring, local, reversible solutions when they satisfy the spec. Do not recommend large refactors merely because they are aesthetically cleaner.

Return:

Decision

ACCEPT, REVISE, or REJECT

Highest-risk decisions

Each item: severity, decision being challenged, failure mode, and why it matters.

Simpler alternative

Only if a materially simpler/safer design exists. Explain trade-offs.

Required plan changes

Concrete changes required before implementation.

Optional improvements

Non-blocking ideas that should not expand current scope unless explicitly approved.

Changes

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.

  1. 16d ago First seen · 42 lines · 51 tokens per session scan A b4a441e5e4fe

Subscribe to this mod's changes

architecture-critic is an agent published in the GitHub repository ddebixx/frontend-template (5 stars, last pushed 17d ago), licensed MIT. It adds 51 tokens to every session and 360 once invoked, about $0.0002 per session on Opus 5.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-10-13.

Related

Other agents, from other repositories

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens