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 Ozzeron/prompt-pack --skill frontend-featuregit clone --depth 1 https://github.com/Ozzeron/prompt-packWrote 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/ozzeron/prompt-pack/frontend-feature)<a href="https://agentmods.dev/skills/ozzeron/prompt-pack/frontend-feature"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/frontend-feature/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/ozzeron/prompt-pack/frontend-feature"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/frontend-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00100 | $0.02654 |
| Opus 5 | $0.00050 | $0.01327 |
| Sonnet 5 | $0.00020 | $0.00531 |
| Haiku 4.5 | $0.00010 | $0.00265 |
Grade A, and why
frontend-feature 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 3d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Feature Builder
You build a frontend feature end-to-end: routing, data fetching, state, forms, validation, UI, error handling, tests. The work spans multiple files and touches several layers, so discipline matters more than ambition: match the project's existing architecture, reuse its primitives, and don't introduce parallel patterns.
When to use
- New page, route, or self-contained feature on the client
- "Add CRUD for X", "build settings for Y", "implement the dashboard for Z"
- Cross-layer work: routing + data + UI together
Do not invoke for:
- Pure visual design without data integration (use
interface/ui-designer) - Single-component changes (just edit it)
- Backend or DB work (use
architecture/backend-api,architecture/database-schema) - Auditing existing code (use
review/frontend-audit)
Scope
In scope:
- Routing / route definition
- Data fetching, mutations, optimistic updates, cache invalidation
- Local + URL + server state coordination
- Forms: schema, validation, submission, errors
- UI: layout, components, states (delegated to
ui-designer) - Types end-to-end (API contract → form → render)
- Loading, empty, error, success paths
- Tests for the feature's behaviour, not its implementation details
Out of scope:
- API contract design — assume one exists or specify what's needed and stop
- Database changes — call out the requirement, don't author the migration
- Cross-cutting infrastructure (auth, theming, analytics) — use what exists, flag gaps
Inherits
meta/engineering-principles— file size, type safety, naming, modern standards.meta/reuse-before-create— the DRY decision flow; every "new" entry in your file plan must satisfy this skill's checks.meta/token-discipline— sample, don't read everything.interface/ui-designer— for the UI portion: creativity calibration, restraint, visual consistency.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -93 lines · +69 tokens per session 10d4695a375d
- 9d ago First seen · 310 lines · 31 tokens per session scan A 7a9c73896bbc
frontend-feature is a skill published in the GitHub repository Ozzeron/prompt-pack (8 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 2,654 once invoked, about $0.0005 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
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
accessibility-i18n
A guide for building accessible and multilingual software. Accessibility means making interfaces usable with tools such as keyboards and screen readers; internationalisation prepares them for different languages, regions, and writing directions.
frontend-architecture
A frontend architecture guide for pages, components, state, data fetching, asynchronous caching, server rendering, runtime settings, translation, server-sent events, performance, accessibility, and validation. Server rendering means preparing page content on the server before the browser displays it.
design-system-architecture
A guide for turning a brand’s visual rules into a reusable design system. Design tokens are shared values such as colours, spacing, and font sizes; components are reusable interface building blocks.
web-runtime-verify
Verify a built web or static frontend at runtime: serve the build on an ephemeral free port, assert page identity FIRST (automatic recovery on a collision or stale server), run the web battery (overflow 320 to 2560, keyboard and focus, console errors, Lighthouse and axe when available), and decide a PASS/FAIL/BLOCKED…
a11y-audit
Senior accessibility auditor mapping a UI surface (screen, flow, or component set) to WCAG 2.2 at a named conformance level (A, AA, AAA). Produces ACCESSIBILITYAUDIT.md, a per-criterion conformance ledger that splits machine-checkable rows from a manual-review queue, with severity and concrete remediation per finding.…