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/effulgent-point/paw/frontendnpx skills add Effulgent-Point/paw --skill frontendgit clone --depth 1 https://github.com/Effulgent-Point/pawWrote 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/effulgent-point/paw/frontend)<a href="https://agentmods.dev/skills/effulgent-point/paw/frontend"><img src="https://agentmods.dev/badge/skills/effulgent-point/paw/frontend.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00614 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
frontend 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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Skill
When to use: React, Vue, or Angular work — component design, accessibility, performance, state management.
Component design
- Composition over inheritance — build complex UI from small, focused components
- Single responsibility — one component, one job. If the name needs "And", split it.
- Props interface — keep it narrow. More than 5-7 props? The component is doing too much.
- Prop drilling limit — more than 2 levels deep? Use context or composition (children pattern).
- Children pattern — prefer
<Layout><Content /></Layout>over render props when possible.
Hooks best practices (React)
- Dependency arrays must be complete — ESLint rule
react-hooks/exhaustive-depsis not optional - Effects clean up — return a cleanup function for subscriptions, timers, event listeners
- Custom hooks — extract reusable stateful logic into
useXxxhooks - Never call hooks conditionally — hooks must be called in the same order every render
- Avoid
useEffectfor derived state — compute it during render instead
Accessibility floor (WCAG 2.1 AA)
These are minimums, not aspirations:
- Every interactive element has an accessible label (
aria-label, associated<label>, or visible text) - Color contrast: 4.5:1 for normal text, 3:1 for large text
- All functionality reachable via keyboard (Tab, Enter, Escape, Arrow keys)
- Focus management: focus moves logically on route change and modal open/close
- ARIA landmarks on major sections (
<main>,<nav>,<aside>) - Images: meaningful
alttext, oralt=""for decorative - Form errors announced to screen readers (
aria-liveorrole="alert")
Performance
- Memoization —
React.memo,useMemo,useCallbackonly where there's measured need. Don't prematurely optimize. - Virtualization — lists >100 items should use
react-windowor similar - Code splitting — at minimum, split at the route level (
React.lazy+Suspense) - Image optimization — responsive sizes, lazy loading below the fold, modern formats (WebP/AVIF)
- Bundle awareness — check import cost. A 500KB library for one function is not worth it.
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.
- 5d ago First seen · 48 lines · 0 tokens per session scan A a8beb85d6ee0
frontend is a skill published in the GitHub repository Effulgent-Point/paw (2 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 614 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
formkit
Use when working with FormKit forms, validation, schema, or custom inputs in React, Vue, or Nuxt projects.
artisan
A production frontend craftsman for React/Vue/Svelte. Responsible for hooks design, state management, Server Components, form handling, and data fetching. Converts Forge prototypes into production-quality code. Use when production frontend implementation is required.
web-component-design
Master React, Vue, and Svelte component patterns including CSS-in-JS, composition strategies, and reusable component architecture. Use when building UI component libraries, designing component APIs, or implementing frontend design systems.
zoom-meeting-sdk-web-component-view
Zoom Meeting SDK Web - Component View. Embeddable Zoom meeting components with Promise-based API for flexible integration. Ideal for React/Vue/Angular apps and custom layouts. Uses ZoomMtgEmbedded with async/await patterns and embeddable UI containers.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.