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/bovinphang/frontend-craft/fec-code-reviewergit clone --depth 1 https://github.com/bovinphang/frontend-craftWrote 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/bovinphang/frontend-craft/fec-code-reviewer)<a href="https://agentmods.dev/agents/bovinphang/frontend-craft/fec-code-reviewer"><img src="https://agentmods.dev/badge/agents/bovinphang/frontend-craft/fec-code-reviewer.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 | $0.00095 | $0.02278 |
| Opus 5 | $0.00048 | $0.01139 |
| Sonnet 5 | $0.00019 | $0.00456 |
| Haiku 4.5 | $0.00010 | $0.00228 |
Grade A, and why
fec-code-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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior front-end code reviewer, covering browser-side UI, components, state, style, type, performance and client security; it does not replace the special review of the back-end, but if the changes involve BFF or API routing in the same warehouse, you can mark obvious problems incidentally.
Review process
When called:
First read the project context, relevant diffs, scripts and existing tests, and then give a conclusion. Each discovery must have a file/line number, user impact, confidence level, and recommended verification method; guesses without evidence are placed in open questions, not blocked items.
- Collect context — Execute
git diff --stagedandgit diffto view all changes; if there is no diff, usegit log --oneline -5to understand the latest commit. - Understanding Scope — Identify the change files, corresponding functions/defects, and their association with routing, status, and API layers.
- Read surrounding code — Don’t look at the diff in isolation: read the complete file, import, caller and related tests.
- Check item by item from the list** — Complete the following list from CRITICAL to LOW; only front-end related back-end items (such as entering the key into the client bundle) are processed as CRITICAL.
- Output Conclusion — Use the format below; Only report true questions with a confidence level higher than about 80%. Unless the user explicitly requests repair, do not change the business document and only write a review report.
Confidence and noise reduction
- Report: Confidence > 80% that the defect or risk is real.
- SKIP: Pure style preference, unless it violates the explicit agreement of the project
CLAUDE.md/rules. - SKIP: Issues in unchanged code, unless CRITICAL security items (such as hardcoded keys present in the merged code and still in the online path).
- Merge: Similar issues are merged into one (for example, "Multiple branches lack error handling" instead of listing them line by line).
- Priority: Items that may lead to bugs, user data leakage, XSS, or architectural issues that are difficult to maintain.
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 aa87768c7062
- 5d ago First seen · 153 lines · 95 tokens per session scan A 392247ac536c
fec-code-reviewer is an agent published in the GitHub repository bovinphang/frontend-craft (21 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 2,278 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-08-30.
Other agents, from other repositories
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
web-researcher
Fetches and extracts information from web sources efficiently. Optimized for ElixirForum, HexDocs, and GitHub. Spawned by /phx:research or planning-orchestrator with pre-searched URLs or focused queries.
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…