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/alonf/specrew/specrew-design-workshopnpx skills add alonf/specrew --skill specrew-design-workshopgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/specrew-design-workshop)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-design-workshop"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-design-workshop.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.00193 | $0.08052 |
| Opus 5 | $0.00097 | $0.04026 |
| Sonnet 5 | $0.00039 | $0.01610 |
| Haiku 4.5 | $0.00019 | $0.00805 |
Grade A, and why
specrew-design-workshop 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-design-workshop
Type: Facilitation Skill Schema: v1 Status: Active design-lifecycle conduct
Purpose
Drive the design lenses as a real, point-of-use workshop — not a checklist skimmed once at launch. Each time you reach a lens, this skill is loaded fresh so the conduct is in focus exactly when you use it. It is self-contained: one load gives you everything you need for the current lens. Because most hosts do not guarantee a fresh reload per turn, re-invoke this skill (or re-read it) at the start of each new lens.
The Big Picture (read this first, every time)
You are facilitating a design conversation with a human, one lens at a time. The lenses live in
extensions/specrew-speckit/knowledge/design-lenses/ (deployed under the project's design-lens catalog):
architecture-core, component-design, requirements-nfr, ui-ux, data-storage, security-compliance,
integration-api, devops-operations, observability-resilience, code-implementation. For each lens you work:
- Load that lens's md (
design-lenses/<lens-id>.md) for its## Design Decision Pointsand## Workshop Conduct— that is the lens's focused agenda. Do not improvise it from memory. - Facilitate the discussion for that lens (the method below).
- Record the decisions + agreement.
- Re-invoke this skill and go to the next lens.
The per-lens knowledge is in the lens md; this skill is the method that ties the lenses together. Keep both in view.
Render before you ask — the question may only reference what is on screen (A6/A7/FR-037). Before you raise ANY confirm/approve question (a structured menu on hosts that preserve the preceding message, or a typed "does this work? / move on? / approve" prompt) about the lens agenda + depths, a per-lens diagram, the component map, an options/trade-off set, or a design verdict — the thing you are asking about MUST already be rendered in your assistant message in THIS exchange, in prose / console-ASCII the human can see. The question may reference ONLY content that is on screen. Never ask from a count ("8 lenses", "13 components"), a summary ("the agenda", "the map"), or a "shown above / as proposed" that was not actually shown. The failure mode this exists to stop is menu-before-render: render + explain, THEN ask. Be verbose — explain the agenda / diagram / map / options fully in prose first, and make the question and choices self-explanatory (not a terse "does this work? — 8 lenses").
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.
- 4d ago First seen · 397 lines · 193 tokens per session scan A 53a262bd69d3
specrew-design-workshop is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 193 tokens to every session and 8,052 once invoked, about $0.0010 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-30.
Other skills, from other repositories
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
hallmark
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.