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 skills/cypsy1714/cchad/react-patterns-skillnpx skills add Cypsy1714/cchad --skill react-patterns-skillgit clone --depth 1 https://github.com/Cypsy1714/cchadWhat 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.00025 | $0.00308 |
| Opus 5 | $0.00013 | $0.00154 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
react-patterns 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.
What it actually says
React patterns
Guidance for writing React that stays readable as it grows.
Components
- Keep components small and single-purpose. If a component does two things, split it.
- Prefer composition (passing children / render props) over configuration via a growing list of boolean props.
- Derive state during render instead of storing values you can compute.
Hooks
- Every
useEffectneeds a clear reason to exist. If it only transforms props into state, you probably don't need it — compute the value inline. - List every dependency an effect reads. Don't silence the linter; fix the dependency.
- Extract reused stateful logic into a custom
useXhook rather than copying effect bodies between components.
State
- Keep state as local as possible; lift it only when two components truly share it.
- Model server data with a data-fetching library (React Query / SWR) instead of
hand-rolled
useEffect+useStateloading flags. - Keep a single source of truth. Don't mirror the same value in two states.
Rendering
- Give lists stable
keys tied to identity, never the array index. - Reach for
useMemo/useCallbackonly when you have a measured performance problem, not by default.
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 First seen · 36 lines · 25 tokens per session scan A 4446e94580c6
react-patterns is a skill published in the GitHub repository Cypsy1714/cchad (1 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 308 once invoked, about $0.0001 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
memory
Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
submit-a-plugin
Submit a bb plugin to the BB Community marketplace. Use whenever a user asks to submit, list, publish, or add a plugin to the BB marketplace, or asks for a marketplace pull request. This skill validates the plugin and release, creates the marketplace entry and icon, and opens the pull request.
secrets
Securely request API keys, access tokens, passwords, webhook secrets, or other credentials and write them to a dotenv file without exposing their values to the agent. Use whenever a task needs a credential that the user must supply.
analyze-bundle
Convert Next.js bundle analyzer data to NDJSON and explore it.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.