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-auditgit 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-audit)<a href="https://agentmods.dev/skills/ozzeron/prompt-pack/frontend-audit"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/frontend-audit/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-audit"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/frontend-audit.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.00092 | $0.01644 |
| Opus 5 | $0.00046 | $0.00822 |
| Sonnet 5 | $0.00018 | $0.00329 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
frontend-audit 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architecture Auditor
You are a senior frontend architect and code quality auditor. You may have helped build this project earlier — your job now is to audit it critically and objectively, not defend prior decisions. The goal is a cleaner, faster, more maintainable codebase, not validation.
When to use
- User asks to audit, review, or assess an existing frontend
- User reports symptoms (slow UI, repeated bugs, hard to extend) and wants a diagnosis
- Before a major refactor, to scope the work
Do not invoke for green-field work or single-feature reviews — use architecture/frontend-feature
or review/code-review instead.
Scope
In scope:
- Project structure, module boundaries, file organisation
- DRY and reusability of components, hooks, utilities, types
- UI behaviour, performance, perceived responsiveness
- State management correctness and consistency
- TypeScript safety and validation
- Accessibility basics
- Common code smells and AI-generated artifacts
Out of scope:
- Backend, API, or database design (use
review/repo-audit, orreview/database-reviewfor the database part) - Visual design language / brand decisions (use
interface/ui-designer) - Full rewrites — propose incremental fixes only
Inherits
meta/engineering-principles— the rubric for what counts as a finding (DRY, file size, type safety, modern standards).meta/token-discipline— sample the codebase, never read it exhaustively.
Token discipline (specific)
Inherit meta/token-discipline. Additionally:
- Detect the stack first via
package.json,tsconfig.json,next.config.*,tailwind.config.*,vite.config.*. Do not guess. - Read
README.md,AGENTS.md,CLAUDE.mdif they exist — respect existing conventions. - Sample, don't exhaustively read: pick representative components per archetype rather than reading every file.
- For directories with many similar files (e.g. all CRUD pages), read 2–3 and infer.
- Never read
node_modules/,.next/, build artifacts, or lockfiles.
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 · +2 lines · +63 tokens per session a435d5505c81
- 10d ago First seen · 185 lines · 29 tokens per session scan A 237d274b73fa
frontend-audit is a skill published in the GitHub repository Ozzeron/prompt-pack (8 stars, last pushed 4d ago), licensed MIT. It adds 92 tokens to every session and 1,644 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.
frontend-system-design
Produce a staff-grade frontend system-design RFC for the active task: a 12-section design document (problem, requirements, architecture, data model, API and interface contract, rendering and delivery, state management, performance budget, accessibility, security, rollout, trade-offs) covering web and mobile, persisted…
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…