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/martinstofko219/agentic-design-toolkit/spec-designnpx skills add martinstofko219/agentic-design-toolkit --skill spec-designgit clone --depth 1 https://github.com/martinstofko219/agentic-design-toolkitWrote 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/martinstofko219/agentic-design-toolkit/spec-design)<a href="https://agentmods.dev/skills/martinstofko219/agentic-design-toolkit/spec-design"><img src="https://agentmods.dev/badge/skills/martinstofko219/agentic-design-toolkit/spec-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.1 | $0.00100 | $0.02190 |
| Opus 5 | $0.00050 | $0.01095 |
| Sonnet 5 | $0.00020 | $0.00438 |
| Haiku 4.5 | $0.00010 | $0.00219 |
Grade A, and why
spec-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 5d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-design
This skill guides building production-ready Angular UI — pages, sections, and reusable components — using the Nextech Design System (@nextech/ui-components). The output is structured, accessible Angular code with mock data, ready for developers to wire up real API calls and logic.
Design input may come from Figma frames (via the Figma MCP), React prototypes in the workspace, written descriptions, or a combination. The Nextech Design System MCP server is the single source of truth for available components, patterns, and tokens. One invocation typically produces a complete page or a coherent, self-contained section; complex apps are built incrementally, section by section, across multiple invocations.
Session mode: Once invoked, this skill stays active for the rest of the session — apply these guidelines to every subsequent build request without re-invocation. On first load, tell the designer the skill is active and remains so until they say "stop spec-design" or "exit skill mode."
Step 1: Verify Prerequisites
Before doing anything else, confirm the required tools and environment are available.
Nextech Design System MCP — attempt to call getComponentDescriptions(). If it fails or is unavailable, stop and ask the user to install @nextech/design-system-mcp; it is required for every build.
Figma MCP — needed only if the user provides a Figma link. If a Figma URL is present but the MCP is unavailable, ask for screenshots or a written description instead.
Angular workspace — confirm @nextech/ui-components is installed and an Angular app shell is running; if not, ask the user to set one up before proceeding.
Step 2: Understand the Design Input
Gather and synthesize all available design references before writing any code.
If the concept itself is unclear — the problem being solved, who the user is, what the layout or behavior should be — suggest running the design-grill skill before building, regardless of what artifacts are provided: a vague description, a low-fidelity sketch without interaction notes, or a Figma frame that doesn't communicate intent all qualify. Reading the artifacts answers what the concept is; design-grill tests whether it should exist in this form. Ordinary missing detail you can just ask about is not a grill trigger, but production code is the most expensive thing in this pipeline to rework — so the bar here is low: if you can't yet make confident decisions about component structure and behavior, grill first. Suggest once, naming the specific gap: this is a nudge, not a gate — if they'd rather build, build, and state the assumption you're proceeding on.
What ships with it
1 file 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.
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.
- 5d ago First seen · 133 lines · 100 tokens per session scan A 07d6482af2de
spec-design is a skill published in the GitHub repository martinstofko219/agentic-design-toolkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 2,190 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
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…