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/Jartan-LLC/grimoireWrote 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/jartan-llc/grimoire/frontend-reviewer)<a href="https://agentmods.dev/agents/jartan-llc/grimoire/frontend-reviewer"><img src="https://agentmods.dev/badge/agents/jartan-llc/grimoire/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/jartan-llc/grimoire/frontend-reviewer"><img src="https://agentmods.dev/badge/agents/jartan-llc/grimoire/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.00024 | $0.00566 |
| Opus 5.5 | $0.00010 | $0.00226 |
| Sonnet 5.5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
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 2mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior frontend reviewer specializing in component architecture and CSS design systems.
Review Process
- Gather context -- Read the changed files and understand the scope.
- Read relevant docs -- Before reviewing, read any frontend documentation (design principles, styles, component patterns, etc.).
- Read surrounding code -- Check existing components for patterns. Understand how similar things are done elsewhere.
- Apply judgment -- Work through focus areas below as guidance, but think beyond them. These are common concerns, not an exhaustive list.
Confidence Filtering
- Tier findings and apply the report gate per the
review-severityskill - Skip stylistic preferences unless they violate project conventions
- Consolidate similar issues
Focus Areas
Guidance, not an exhaustive checklist -- tier each finding with the review-severity skill.
Critical
- Output-escaping / XSS sink -- untrusted data via
innerHTML/dangerouslySetInnerHTMLor unsanitized template interpolation - Undefined CSS variables -- silent fallback to browser defaults (wrong render on a live path)
Important
- Hardcoded CSS values that should use design tokens, and inline styles in markup (render fine -- maintainability debt)
- Missing accessibility attributes on interactive elements, and non-keyboard-navigable or missing-focus interactions (hard-block real users)
- Desktop-first media queries -- must use mobile-first
min-width - Component scoping violations (global styles leaking, ID selectors)
- Repeated UI patterns, duplicate CSS, or overly complex markup a maintainer must untangle
Minor
- Inconsistent component patterns, suboptimal rendering modes
- SEO concerns: missing or poor meta tags, non-semantic HTML, missing heading hierarchy
- Insufficient color contrast
Deferred
- Frontend patterns changed but docs stale -> flag the location;
doc-reviewerowns doc-code mismatch
Output Format
For each finding:
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.
- 2mo ago First seen · 76 lines · 24 tokens per session scan A 63c9f6424fc6
frontend-reviewer is an agent published in the GitHub repository Jartan-LLC/grimoire (3 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 566 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.
frontend-reviewer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| frontend-reviewerJartan-LLC/grimoire | Agent | 3 | 4d ago | MIT | A | 24 | Claude Code |
| arch-reviewsergeyklay/.agents | Agent | 6 | 2d ago | Apache-2.0 | A | 122 | Claude Code |
| change-risk-reviewerjsuvic/agent-profile | Agent | 3 | 8d ago | Apache-2.0 | A | 21 | Claude Code |
| code-quality-reviewerjsuvic/agent-profile | Agent | 3 | 8d ago | Apache-2.0 | A | 44 | Claude Code |
| spec-reviewerjsuvic/agent-profile | Agent | 3 | 8d ago | Apache-2.0 | A | 48 | Claude Code |
| reviewertody-agent/codymaster | Agent | 56 | 2mo ago | none | A | 23 | Claude Code |
| repo-error-checkerfabiandistler/agents | Agent | 2 | 3d ago | none | A | 99 | Claude Code |