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 agentmods add skills/douglance/sdlc-plugin/frontend-designnpx skills add douglance/sdlc-plugin --skill frontend-designgit clone --depth 1 https://github.com/douglance/sdlc-pluginWrote 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/douglance/sdlc-plugin/frontend-design)<a href="https://agentmods.dev/skills/douglance/sdlc-plugin/frontend-design"><img src="https://agentmods.dev/badge/skills/douglance/sdlc-plugin/frontend-design.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 | $0.00025 | $0.02519 |
| Opus 5 | $0.00013 | $0.01260 |
| Sonnet 5 | $0.00005 | $0.00504 |
| Haiku 4.5 | $0.00003 | $0.00252 |
Grade A, and why
frontend-design 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create an interface that feels authored by a strong human designer, not averaged from template patterns. In order:
- Understand the context — purpose, users, framework, performance budget, accessibility requirements, brand anchors (adjectives, references, taboos). Check the project's existing design system / component library before authoring custom markup. Ask only for what blocks correct execution.
- Commit to a specific art direction — derive it from the subject, then execute it with precision. Bold maximalism and refined minimalism both work; intentionality is mandatory. Do not force novelty through arbitrary extremity, and do not let unrelated briefs converge on the same theme, fonts, palette, layout, assets, or energy.
- Invent a signature element — one unforgettable hook that is functional, not decorative.
- Define design tokens before layout — all styling flows from tokens.
- Build to the hard rules below (typography, color, layout, motion, texture) with every interaction state and failure path designed.
- Run the final quality gate — if any check fails, the output is invalid. Then verify visually per the
visual-designskill: render, screenshot, judge the whole composition.
Deliver: an art-direction brief (direction, type pairing, palette logic, motion grammar, material choice), complete runnable code matching the requested scope, and extension notes on growing tokens/components/states without breaking coherence.
Art directions (inspiration only — never a menu to rotate through)
Editorial magazine (asymmetric grids, typographic authority, dramatic whitespace) · Neo-brutalist industrial (hard edges, utilitarian labels, raw materials) · Luxury refined (restraint, premium materials, invisible complexity) · Retro-futurist CRT (scanlines, angular geometry, phosphor glow) · Organic tactile (paper grain, irregular shapes, handmade warmth) · Punk zine (collage energy, raw texture, deliberate imperfection) · Bauhaus precision (geometric discipline, functional clarity, primary colors) · Psychedelic surreal (controlled chaos, vivid contrast, fluid forms).
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 First seen · 138 lines · 25 tokens per session scan A 59cb65c6bd3b
frontend-design is a skill published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 2,519 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…