agentmods.dev

bayes-platform: Skill for Claude Code

.claude/skills/check-use-state/SKILL.md

check-use-state is a skill for Claude Code from bayesimpact/bayes-platform. It costs 30 tokens per session (254 once invoked), scanned A, original, MIT.

A static check for frontend components that counts React useState hooks and reports files using more than two. React is a JavaScript interface library, and useState stores local values that can change on screen.

In plain words
What is it for?
Use it to scan TSX files, list violating file paths and line numbers, and produce a count of checked files and violations.
Why use it?
It identifies components with many separate local state variables, which may be harder to maintain and may need a shared state approach or refactoring.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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

not rated 23repo yesterday A scan 30 tokens original MIT
View source ↗ bayesimpact/bayes-platform bayesimpact.org
Reuse

Borrowing it

Nothing to install: this file belongs to bayesimpact/bayes-platform. 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/bayesimpact/bayes-platform/main/.claude/skills/check-use-state/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bayesimpact/bayes-platform

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 check-use-state

README.md
[![agentmods](https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/check-use-state/github.svg)](https://agentmods.dev/skills/bayesimpact/bayes-platform/check-use-state)
Your own site
<a href="https://agentmods.dev/skills/bayesimpact/bayes-platform/check-use-state"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/check-use-state/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 check-use-state

Your own site · 80×15
<a href="https://agentmods.dev/skills/bayesimpact/bayes-platform/check-use-state"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/check-use-state.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 254 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 original 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.00030 $0.00254
Opus 5.5 $0.00012 $0.00102
Sonnet 5.5 $0.00006 $0.00051
Haiku 4.5 $0.00003 $0.00025

Measured 1mo ago against content hash c73944dc06a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

check-use-state 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 1mo 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/check-use-state/SKILL.md · 24 lines

What it actually says

Check that no frontend component uses more than 2 useState hooks. A component with too many local state variables is a sign it should be refactored (custom hook, context, or state manager).

Steps

  1. Use the Grep tool to find all useState( occurrences across apps/web/src/**/*.tsx files, with output mode content and line numbers enabled, so you can see each match with its file path and line number.

  2. Group the results by file. For each file, count the number of lines that contain useState( — ignore import lines (lines containing import).

  3. Report the results in two sections:

Violations (> 2 useState)

List every file that has more than 2 useState calls. For each file show:

  • The relative file path (from repo root)
  • The count
  • The line numbers of each useState call

Summary

"X files checked, Y violations found." If there are no violations, congratulate the user.

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. 1mo ago First seen · 24 lines · 30 tokens per session scan A c73944dc06a3

Subscribe to this mod's changes

check-use-state is a skill published in the GitHub repository bayesimpact/bayes-platform (23 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 254 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-09-14.

FrontendReact
Related

check-use-state compared with skills from other repositories

check-use-state next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
check-use-statebayesimpact/bayes-platformSkill23yesterdayMITA30Claude Code
build-ghost-appTryGhost/GhostSkill56kyesterdayMITA44Claude Code, Codex
chakra-ui-builderchakra-ui/chakra-uiSkill41kyesterdayMITA214Claude Code, Codex
material-ui-tailwindmui/material-uiSkill99kyesterdayMITA67Claude Code, Codex
fuzzy-rankingTanStack/tableSkill29k4d agoMITA62Claude Code, Codex
r3f-best-practiceszebbern/claude-code-guideSkill4.7k3d agoMITA74Claude Code, Codex
git-safetytamagui/tamaguiSkill14ktodayMITA0Claude Code