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 skills add medy-gribkov/arcana --skill frontend-code-reviewgit clone --depth 1 https://github.com/medy-gribkov/arcanaWrote 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/medy-gribkov/arcana/frontend-code-review)<a href="https://agentmods.dev/skills/medy-gribkov/arcana/frontend-code-review"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/frontend-code-review/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/skills/medy-gribkov/arcana/frontend-code-review"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/frontend-code-review.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.00036 | $0.02423 |
| Opus 5 | $0.00018 | $0.01211 |
| Sonnet 5 | $0.00007 | $0.00485 |
| Haiku 4.5 | $0.00004 | $0.00242 |
Grade A, and why
frontend-code-review 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 9d 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 — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Code Review
Review Process
This skill reviews .tsx, .ts, and .js files against three categories:
- Code Quality - Consistent patterns, maintainability
- Performance - React rendering optimization
- Business Logic - Domain-specific rules
Two review modes:
- Pending-change review - Scan staged/modified files before commit
- File-targeted review - Review specific files the user names
Code Quality Rules
Rule 1: Conditional Classnames (URGENT)
Requirement: Use cn() utility for all conditional CSS, not ternaries or string concatenation.
BAD:
// Manual ternary
<div className={isActive ? 'text-primary-600' : 'text-gray-500'}>
// String concatenation
<div className={'bg-white ' + (isError ? 'border-red-500' : '')}>
// Template literal
<div className={`text-base ${highlighted && 'font-bold'}`}>
GOOD:
import { cn } from '@/utils/classnames';
<div className={cn(
'text-base',
isActive && 'text-primary-600',
!isActive && 'text-gray-500'
)}>
<div className={cn(
'bg-white',
isError && 'border-red-500'
)}>
Why urgent: Inconsistent patterns make global style changes difficult.
Rule 2: Tailwind-First Styling (URGENT)
Requirement: Prefer Tailwind utilities over .module.css files unless Tailwind cannot achieve the effect.
BAD:
// styles.module.css
.button {
padding: 0.75rem 1.5rem;
background-color: #3b82f6;
border-radius: 0.5rem;
}
// Component.tsx
import styles from './styles.module.css';
<button className={styles.button}>Click</button>
GOOD:
<button className="px-6 py-3 bg-blue-500 rounded-lg hover:bg-blue-600">
Click
</button>
When CSS modules are acceptable:
- Complex animations requiring
@keyframes - Browser-specific hacks
- Third-party library style overrides
Rule 3: ClassName Ordering for Overrides
Requirement: Place incoming className prop AFTER component's own classes.
BAD:
const Button = ({ className }: { className?: string }) => {
return (
<div className={cn(className, 'bg-primary-600 text-white px-4 py-2')}>
{/* Consumer can't override bg-primary-600 */}
</div>
);
};
// Consumer tries to change background
<Button className="bg-red-500" /> {/* Won't work */}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 388 lines · 36 tokens per session scan A cdea18277e7a
frontend-code-review is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,423 once invoked, about $0.0002 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-31.
Other skills, from other repositories
generic-react-code-reviewer
Review React/TypeScript code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Enforces TypeScript strict mode, GPU-accelerated animations, WCAG AA accessibility, bundle size limits, and surgical simplicity. Use when completing features, before commits, or…
react-component
Build production-ready React components — hooks, context, accessibility, TypeScript types, and Storybook stories.
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
react-patterns
React 19 performance patterns and composition architecture for Vite + Cloudflare projects. 50+ rules ranked by impact — eliminating waterfalls, bundle optimisation, re-render prevention, composition over boolean props, server/client boundaries, and React 19 APIs. Use when writing, reviewing, or refactoring React…
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
generic-react-feature-developer
Guide feature development for React applications with architecture focus. Covers Zustand/Redux patterns, IndexedDB usage, component systems, lazy loading strategies, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.