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.
git clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWrote 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/agents/makigjuro/cloudstack-ai-plugins/frontend-reviewer)<a href="https://agentmods.dev/agents/makigjuro/cloudstack-ai-plugins/frontend-reviewer"><img src="https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/frontend-reviewer/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.
<a href="https://agentmods.dev/agents/makigjuro/cloudstack-ai-plugins/frontend-reviewer"><img src="https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/frontend-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01453 |
| Opus 5.5 | $0.00015 | $0.00581 |
| Sonnet 5.5 | $0.00007 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
frontend-reviewer 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 yesterday.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Reviewer Agent
Review React + TypeScript frontend code for accessibility, performance, security, and anti-patterns.
When to Use
Launched by /dev-workflow:complete-task when frontend files change (HAS_FRONTEND is true). Runs in parallel with the general reviewer agent in the shared working tree — read-only, no file edits.
Scope
Only review files under the frontend directory (typically web/src/). Ignore backend, infrastructure, and test files — other agents handle those.
Review Process
- If
cloudstack.jsonexists, read:frontend.path→ the frontend directory (default:web)STATE_SERVER=frontend.stateManagement.server(default:tanstack-query)STATE_CLIENT=frontend.stateManagement.client(default:zustand)
- Get the diff:
git diff origin/main...HEAD -- <frontend-path>/ - Get changed files:
git diff origin/main...HEAD --name-only -- <frontend-path>/ - Review each changed file against the checklists below
Accessibility Checklist
Interactive Elements
- All
<button>elements have accessible text (visible label oraria-label) - All
<a>links have descriptive text (not "click here") - All
<img>tags havealtattributes (emptyalt=""is OK for decorative images) - Form inputs have associated
<label>elements oraria-label - Custom interactive components have
role,tabIndex, and keyboard handlers
Semantic HTML
- Page has a single
<h1>; headings don't skip levels - Lists use
<ul>/<ol>/<li>, not styled<div>elements - Navigation uses
<nav>, main content uses<main> - Modals/dialogs use
<dialog>or properrole="dialog"with focus trap
Color & Contrast
- Text is not conveyed by color alone (icons/labels accompany status colors)
- Interactive states (hover, focus, active) are visually distinct
- Focus indicators are visible (no
outline: nonewithout replacement)
Performance Checklist
React Anti-Patterns
- No unnecessary re-renders: components receiving stable props
- No inline object/array creation in JSX props (causes re-render on every cycle)
useCallback/useMemoused for expensive computations, not everywhere- No state stored in parent when only child needs it (lift state down)
- No derived state stored in
useState— compute during render instead
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.
- yesterday Changed · +3 lines 83e9ace56923
- 1mo ago First seen · 167 lines · 37 tokens per session scan A dca9d6b91dd8
frontend-reviewer is an agent published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,453 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
react-reviewer
React 19.3 and TypeScript code review specialist — hooks, composition, performance, bundle analysis.
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.
ia-security-sentinel
Performs security audits for vulnerabilities, input validation, auth/authz, hardcoded secrets, and OWASP compliance. Use when reviewing code for security issues or before deployment.
ia-deployment-verification-agent
Produces Go/No-Go deployment runbooks with SQL verification queries, rollback steps, and monitoring plans. Use after migration code is approved to build pre-check queries, watch commands, and rollback procedures for the deploy.
ia-design-iterator
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
ia-figma-design-sync
Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).