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 sungurerdim/dev-skills --skill ds-frontendgit clone --depth 1 https://github.com/sungurerdim/dev-skillsWrote 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/sungurerdim/dev-skills/ds-frontend)<a href="https://agentmods.dev/skills/sungurerdim/dev-skills/ds-frontend"><img src="https://agentmods.dev/badge/skills/sungurerdim/dev-skills/ds-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.1 | $0.00043 | $0.05802 |
| Opus 5 | $0.00022 | $0.02901 |
| Sonnet 5 | $0.00009 | $0.01160 |
| Haiku 4.5 | $0.00004 | $0.00580 |
Grade A, and why
ds-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 4d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ds-frontend
Hardcoded colors, inconsistent spacing, missing focus states, broken dark mode — design systems exist to prevent these. This skill enforces them in code.
Frontend Design Quality — design system audit, token enforcement, component states, accessibility, responsive layout, theming.
Completion Evidence — applies to every phase: Report
done/OKonly with the machine-checkable evidence the gates name — the exact command run and its observed output (orfile:linediff). Missing evidence → reportINCOMPLETEplus what is missing. Self-assessment is never evidence. (This band repeats at file end by design — both copies are normative.)
Triggers
User runs /ds-frontend, or asks to audit UI/design-system/components/a11y/WCAG/contrast/dark-mode/responsive/tokens, or create a design system; or the project contains frontend framework indicators (React, Vue, Svelte, Astro, SolidJS, htmx, Angular, Flutter, RN, SwiftUI, Compose).
Triggers — INVOKE / DON'T INVOKE
| INVOKE | DON'T INVOKE |
|---|---|
| "audit design system / tokens / hardcoded colors" | "audit business logic" (→ ds-review) |
| "WCAG / a11y technical audit (contrast, focus, ARIA)" | "regulatory a11y framing (EAA, ADA)" (→ ds-compliance --a11y) |
| "generate design tokens / set up theming" | "mobile gestures, permissions, store" (→ ds-mobile) |
| "review component states (empty/loading/error)" | "fix type errors in components" (→ ds-fix) |
| "audit stale/stub routes, dead or mismatched buttons" | "chart/dataviz color palette selection" (→ dataviz) |
Contract
Dimensions: A5 (ux scope), A6 (UI), A7 (implementation), A9 (conditional ecosystem rules), D10 (admin UI)
- Audits UI/UX quality across web, mobile, desktop UI — only touches UI-layer code (styles, components, tokens, ARIA); business + backend untouched.
- Privacy/PII data-handling audit is out of scope:
/ds-compliancepresent → advisory-handoff; absent → gap-note[privacy] not analyzed — requires /ds-compliance. Never runs its own privacy detector. - Standalone. Uses blueprint profile or
ds/audit/findings.mdwhen available; own analysis when absent. - State-qualifying: scope-by-scope progress exists nowhere else — an interrupted run would re-scan from zero without it. Persists to
ds/audit/frontend.jsonwith the run'sgit_hash; applied fixes land in the working tree, git is the durable record. Deleted when the Summary completes. - Full accounting enforced: every finding and planned check ends in an explicit disposition (fixed / skipped + reason / only you can do); summary totals balance.
- Pre-existing / out-of-scope errors detected during work are NOT skipped — fixed inline or escalated with concrete blocker.
What ships with it
9 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.
- README.md 2.9 KB
- references/aesthetics-presets.md 6.7 KB
- references/controlled-vs-innovative.md 5.9 KB
- references/rules-accessibility.md 26 KB
- references/rules-components.md 39 KB
- references/rules-design-system.md 17 KB
- references/rules-responsive.md 26 KB
- references/rules-scheduling.md 11 KB
- references/rules-ux.md 52 KB
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.
- 4d ago Changed · -44 lines 5745afc45baf
- 7d ago First seen · 274 lines · 43 tokens per session scan A bf47a3288c52
ds-frontend is a skill published in the GitHub repository sungurerdim/dev-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 5,802 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
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.
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.
ring:checking-frontend-quality
Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…
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.
ux-ui
Use this agent when you need to design, audit, migrate, rewire, or rewrite UX/UI.