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 andresquirogadev/skillsense --skill reactgit clone --depth 1 https://github.com/andresquirogadev/skillsenseWrote 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/andresquirogadev/skillsense/react)<a href="https://agentmods.dev/skills/andresquirogadev/skillsense/react"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/react/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/andresquirogadev/skillsense/react"><img src="https://agentmods.dev/badge/skills/andresquirogadev/skillsense/react.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.00000 | $0.00464 |
| Opus 5.5 | $0.00000 | $0.00186 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
react 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Skill
You are working in a React codebase. Apply these patterns and conventions.
Component Design
- Write functional components with named exports. Avoid class components.
- Keep components small and focused: one concern per component.
- Extract reusable logic into custom hooks (
useprefix, return an object for multiple values). - Co-locate component state as close as possible to where it is used.
Hooks
- Follow the Rules of Hooks: only call hooks at the top level, never inside conditions or loops.
- Use
useStatefor simple local state;useReducerfor complex state with multiple sub-values. - Use
useCallbackto stabilize callbacks passed as props to memoized children. - Use
useMemoonly when profiling shows an actual performance problem. - Prefer
useId()over manual IDs to avoid hydration mismatches.
State Management
- For global state, prefer React Context +
useReducerfor small apps; use Zustand or Jotai for larger ones. - Avoid prop drilling more than 2–3 levels deep — reach for Context or a state library.
- Keep server state in a dedicated library (TanStack Query, SWR) rather than manually managing loading/error/data.
React 19 Features
- Use
useActionStatefor form actions and loading states — replacesuseFormState. - Use
use(promise)to read async data from Server Components passed as props. - Use
useOptimisticfor instant UI feedback on mutations. refis now a regular prop; no need forforwardRefin React 19.
Performance
- Wrap expensive pure components with
React.memo. - Use
keyon list items; never use array index as key for dynamic lists. - Use
<Suspense>for lazy-loaded components and async operations. - Use
startTransitionto mark non-urgent state updates and keep the UI responsive.
Patterns to Avoid
- Never mutate state directly — always return a new value.
- Never use
indexas key in a list that can be reordered or filtered. - Never fetch data inside
useEffectwithout cleanup; prefer TanStack Query. - Never create components inside render — they will remount on every render.
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.
- 1mo ago First seen · 46 lines · 0 tokens per session scan A 2513f94f4f61
react is a skill published in the GitHub repository andresquirogadev/skillsense (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 464 tokens. 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
ask-sonner
Sonner, the React toast library: mounting Toaster once, toast() calls, promise and loading toasts, updating, dismissing, styling, theming, dark mode, positioning. Use when toasts do not appear, appear twice, sit behind a modal, ignore Tailwind classes, or do nothing from a server action.
plan-review
Criteria for reviewing implementation plans against quality standards.
agent-dependencies
Perform one conservative dependency or toolchain upgrade in the Elements monorepo and open a validated pull request. Use for nightly or unattended dependency maintenance, outdated package checks, first-party actions/ GitHub Actions updates, and pinned mise tool updates. Use the github-dependabot skill instead when the…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
authoring-patterns
Convert validated playground templates or HTML compositions into reusable pattern files (.examples.ts) in the pattern library. Use this skill whenever the user wants to save, persist, store, or catalog a template, prototype, composition, or playground result as a reusable pattern. Trigger on phrases like "save as…
igniteui-blazor-generate-from-image-design
Implement Blazor application views from design images using Ignite UI Blazor components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working…