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 Samuel0101010/wisp-orchestrator --skill frontend-qualitygit clone --depth 1 https://github.com/Samuel0101010/wisp-orchestratorWrote 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/samuel0101010/wisp-orchestrator/frontend-quality)<a href="https://agentmods.dev/skills/samuel0101010/wisp-orchestrator/frontend-quality"><img src="https://agentmods.dev/badge/skills/samuel0101010/wisp-orchestrator/frontend-quality/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/samuel0101010/wisp-orchestrator/frontend-quality"><img src="https://agentmods.dev/badge/skills/samuel0101010/wisp-orchestrator/frontend-quality.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.00029 | $0.00401 |
| Opus 5 | $0.00015 | $0.00200 |
| Sonnet 5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
frontend-quality 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 9d 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.
What it actually says
Every UI you ship must clear this bar. Check each point before finishing:
- All states exist. Loading, empty, error, and success — every view handles all four. An unhandled fetch error or a blank empty screen is a defect, not a nice-to-have.
- Responsive by default. Verify the layout at narrow (~360px), medium (~768px), and wide (~1280px). Nothing overlaps, nothing overflows horizontally, touch targets stay usable.
- Accessible basics. Interactive elements are real buttons/links with accessible names; form fields have labels; contrast is readable in both light and dark themes if the app has them; keyboard focus is visible and reaches everything clickable.
- Consistent, not creative. Reuse the project's existing spacing, colors, type scale, and components. If a design system or token file exists, every value comes from it — no hardcoded one-off hex colors or magic pixel values.
- Text is real. No lorem ipsum, no untranslated placeholder keys, no truncated labels. Long content (names, numbers, translations) must not break the layout.
- Interaction feedback. Buttons show pending state during async work; destructive actions confirm; errors tell the user what to do next in plain language, not error codes.
When a checklist point is impossible to verify in this environment, note it explicitly in your handoff instead of silently skipping 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.
- 9d ago First seen · 33 lines · 29 tokens per session scan A ed3ab4d05467
frontend-quality is a skill published in the GitHub repository Samuel0101010/wisp-orchestrator (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 29 tokens to every session and 401 once invoked, about $0.0001 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
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
design-system
Use when defining or extending design tokens and the shared component library — by product-designer when writing docs/13-design-tokens.md and docs/14-components.md, and by any IC about to add a component. Triggers the moment a value would be hardcoded instead of named, or a one-off component would be created instead…
interaction-motion
Use when specifying or reviewing motion and interaction feel — transitions, gestures, feedback timing, loading and progress. Invoked by product-designer while composing screens and by any IC implementing an animated surface. Triggers whenever something moves, and whenever something takes long enough that the user must…
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live Figma runtime.
ui-design-system
Use this skill when creating, extending, or auditing a product UI system. It adapts Better Design-style design-system discipline without requiring an external runtime package.