carmenta: Skill for Claude Code

.claude/skills/vercel-react-best-practices/SKILL.md

vercel-react-best-practices is a skill for Claude Code from carmentacollective/carmenta. It costs 44 tokens per session (1,451 once invoked), scanned A, original, no licence file.

A set of guidelines for writing, reviewing, and refactoring React or Next.js code, with attention to speed and data loading.

In plain words
What is it for?
Use it when improving React performance, fixing unnecessary re-renders, reducing bundle size, or changing data-fetching patterns.
Why use it?
It helps identify slow rendering, oversized browser code, repeated work, and inefficient data requests.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is carmentacollective/carmenta's own configuration. It tells Claude Code how to work on carmenta 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 carmenta configures →

Reuse

Borrowing it

Nothing to install: this file belongs to carmentacollective/carmenta. 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/carmentacollective/carmenta/main/.claude/skills/vercel-react-best-practices/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/carmentacollective/carmenta

Made for: Claude Code.

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 vercel-react-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/carmentacollective/carmenta/vercel-react-best-practices/github.svg)](https://agentmods.dev/skills/carmentacollective/carmenta/vercel-react-best-practices)
Your own site
<a href="https://agentmods.dev/skills/carmentacollective/carmenta/vercel-react-best-practices"><img src="https://agentmods.dev/badge/skills/carmentacollective/carmenta/vercel-react-best-practices/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 vercel-react-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/carmentacollective/carmenta/vercel-react-best-practices"><img src="https://agentmods.dev/badge/skills/carmentacollective/carmenta/vercel-react-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,451 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 unknown 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.00044 $0.01451
Opus 5 $0.00022 $0.00726
Sonnet 5 $0.00009 $0.00290
Haiku 4.5 $0.00004 $0.00145

Measured 9d ago against content hash 3a4a11a03fde, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vercel-react-best-practices 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.

.claude/skills/vercel-react-best-practices/SKILL.md · 137 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 9d ago First seen · 137 lines · 44 tokens per session scan A 3a4a11a03fde

Subscribe to this mod's changes

vercel-react-best-practices is a skill published in the GitHub repository carmentacollective/carmenta (2 stars, last pushed 2mo ago), with no licence file. It adds 44 tokens to every session and 1,451 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.