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 lazysheep-z/apdr-product-design-runtime --skill frontend-code-reviewergit clone --depth 1 https://github.com/lazysheep-z/apdr-product-design-runtimeWrote 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/lazysheep-z/apdr-product-design-runtime/frontend-code-reviewer)<a href="https://agentmods.dev/skills/lazysheep-z/apdr-product-design-runtime/frontend-code-reviewer"><img src="https://agentmods.dev/badge/skills/lazysheep-z/apdr-product-design-runtime/frontend-code-reviewer/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/lazysheep-z/apdr-product-design-runtime/frontend-code-reviewer"><img src="https://agentmods.dev/badge/skills/lazysheep-z/apdr-product-design-runtime/frontend-code-reviewer.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.00030 | $0.00545 |
| Opus 5 | $0.00015 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
apdr-frontend-code-reviewer 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Code Reviewer (APDR)
Optional gate within stage: frontend_codegen. Run after code generation, before CodeBundle approval.
This skill does NOT create a separate pipeline stage. It enhances the frontend_codegen phase.
External references
- shadcn-ui/ui 117k★ -- UI component patterns with CLI, radix-based accessibility
- microsoft/playwright 91k★ -- accessibility tree audit, component testing
- radix-ui/primitives 19k★ -- accessible headless components, patterns reference
Workflow
-
get_latest_artifact -- CodeBundle, UIDesignSpec, DesignReviewReport
-
Navigate to CodeBundle.rootPath and run checks:
a) Component structure check
- Every UI spec component maps to a React component file
- File naming convention: PascalCase.tsx
- Component is exported, has proper TypeScript types
- Reference: shadcn-ui component patterns
b) Accessibility check
- All interactive elements have aria attributes or use semantic HTML
- Forms have associated labels
- Images have alt text or aria-hidden
- Color is not the only differentiator
- Reference: radix-ui primitives for accessible patterns
c) Responsive check
- CSS uses relative units (rem, em, %), not fixed px for layout
- Media queries or container queries present for breakpoints
- No horizontal scroll on 320px viewport
d) Performance check
- No inline styles for repeated elements -- use CSS classes
- Images have width+height attributes
- Bundle size checklist: lazy loading for heavy components
-
Write issues to CodeBundle provenance.notes
-
Update CodeBundle artifact if fixable issues are found
Do not
- Block the pipeline for style preferences -- only structural issues
- Re-run tests (they are the test-strategy skill's job)
- Evaluate backend code -- this is frontend-only
References
- shadcn-ui/ui 117k★
- radix-ui/primitives 19k★
- microsoft/playwright 91k★
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.
- 11d ago First seen · 58 lines · 30 tokens per session scan A 69a48de34892
apdr-frontend-code-reviewer is a skill published in the GitHub repository lazysheep-z/apdr-product-design-runtime (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 545 once invoked, about $0.0002 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
qt-qml-review
Invoke when the user asks to review, check, audit, or look over Qt6 QML code -- or suggest before committing. Runs deterministic linting (47+ rules) then six parallel deep- analysis agents covering bindings, layout, loaders, delegates, states, and performance. Optionally invokes system qmllint for type-level checks.…
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence. Do not use for generic code review, PR review…
frontend-architecture
Frontend component architecture review — dispatch the component-architecture-review agent over the frontend component files to catch reusable components that should be extracted, duplicated UI patterns, prop drilling, component-granularity problems, and inconsistent component APIs as a frontend evolves. Use when the…
review-persistence-security-resources
Normative reviewer for persistence, settings, secrets, logging hygiene, resources, caches, cross-platform behavior and long-lived state in the explyt/spring-plugin IntelliJ plugin. Use when reviewing changes that touch PersistentStateComponent, settings UI, credentials, caches, service fields, logging, file paths…