agentmods.dev

specmanager-design

specmanager-design is a command for Claude Code from joanseg/specmanager. It costs 44 tokens per session (628 once invoked), scanned A, original, MIT.

A command that creates high-fidelity HTML screen mockups for a SpecManager feature using a designer subagent. It checks whether the feature is ready and whether a design draft already exists before creating one.

In plain words
What is it for?
Use it to design feature screens from an approved PRD, with optional architecture and screenshot context.
Why use it?
It provides a visual design stage for a feature before planning can proceed, while avoiding duplicate drafts.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Part of the specmanager plugin — 9 commands, 7 agents, 1 hook, 1 MCP server shipped together

not rated 23repo changed 22d ago A scan 44 tokens original MIT

Good fit Use it to design feature screens from an approved PRD, with optional architecture and screenshot context.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/joanseg/specmanager/specmanager-design
View source ↗ joanseg/specmanager specmanager.org
Install

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.

Clone the repo
git clone --depth 1 https://github.com/joanseg/specmanager

Made for: Claude Code.

Or install specmanager, the plugin that ships this one along with the rest of its 9 commands, 7 agents, 1 hook, 1 MCP server.

Wrote 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.

agentmods badge for specmanager-design

README.md
[![agentmods](https://agentmods.dev/badge/commands/joanseg/specmanager/specmanager-design/github.svg)](https://agentmods.dev/commands/joanseg/specmanager/specmanager-design)
Your own site
<a href="https://agentmods.dev/commands/joanseg/specmanager/specmanager-design"><img src="https://agentmods.dev/badge/commands/joanseg/specmanager/specmanager-design/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.

agentmods 80×15 button for specmanager-design

Your own site · 80×15
<a href="https://agentmods.dev/commands/joanseg/specmanager/specmanager-design"><img src="https://agentmods.dev/badge/commands/joanseg/specmanager/specmanager-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 628 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00628
Opus 5.5 $0.00018 $0.00251
Sonnet 5.5 $0.00009 $0.00126
Haiku 4.5 $0.00004 $0.00063

Measured 22d ago against content hash acbfa36048b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

specmanager-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 22d 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.

plugins/specmanager/commands/specmanager-design.md · 19 lines

How it starts

The opening of the file, as written. The whole thing — 19 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design the screens for the feature: $ARGUMENTS.

Steps

  1. Resolve → gate → no duplicate. list_features, matching id/slug against the first whitespace-separated token of the argument (anything after it is extra context to forward to the subagent); if none match, ask the user to clarify and stop. Then check_gate({ featureId, stage: "design" }) — open once the PRD is approved; Architecture is not required, design can run in parallel with it. If closed, report reason and stop. Then list_documents({ featureId, stage: "design" }) — if a doc exists, point the user at the panel to edit, or delete the file before regenerating. Don't duplicate.
  2. Look up PRD and Architecture ids to pass into the subagent prompt (list_documents per stage). Architecture may be absent or in draft — pass null if so.
  3. Collect attachments. If the user pasted screenshot paths in the conversation before invoking the command, list them — the designer uses them as visual reference and may inline them as data URIs. If no attachments, the designer works from the PRD + DESIGN.md alone. Optional design reference (R5/AC7): when docs/DESIGN.md holds only placeholder/# TODO tokens, the designer may invite an optional design reference (a screenshot/example through this same attachment path) to ground a synthesized token system — always optional, never required; the designer proceeds and synthesizes if none is given.
  4. Invoke the subagent. Use the Task tool with subagent_type: "designer" and a prompt carrying: the feature id/title/slug, the PRD id + version, the Architecture id + version (if any), the screenshot paths the user attached (if any), and any extra context given after the feature id. The designer reads the upstream docs and ./docs/DESIGN.md, designs the actual screens as one self-contained HTML file (high-fi mockups stacked with explanatory notes), and calls create_design_brief itself.
  5. Report. Document id + file path (design/mockups.html). Suggest opening it in the board — the doc panel renders the stacked mockups in a sandboxed iframe preview.

Read the full file on GitHub · 19 lines

Changes

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.

  1. 22d ago Changed · -11 lines acbfa36048b9
  2. 1mo ago First seen · 30 lines · 44 tokens per session scan A ec3aad513f8c

Subscribe to this mod's changes

specmanager-design is a command published in the GitHub repository joanseg/specmanager (23 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 628 once invoked, about $0.0002 per session on Opus 5.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.

Claude CodeDesign and UXai-agentsai-codingclaude-code-pluginmcpspec-driven-development
Related

Other commands, from other repositories

design-bootstrap

Bootstrap a design system from a Figma file via MCP: extract token variables, identify components, scaffold foundation docs and a component inventory. Use when starting a new project with a Figma file. Do not use when docs exist or there is no Figma file.

Mozurok/fhorja.dev · 0 tokens

ccc-theme

List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.

KevinZai/commander · 47 tokens

atom-audit-fleet

Audit every atom in parallel against the component guidelines, one worker per small group, merging rows into one ATOMAUDIT.md table (orchestrator-workers variant of atom-audit). Use when the atom count is 6 or more and COMPONENTGUIDELINES.md exists. Do not use below 6 atoms (use atom-audit single-agent), without…

Mozurok/fhorja.dev · 102 tokens

mcp-server-vet

Read-only inspection of a third-party MCP server BEFORE it is added or trusted: scans tool descriptions and scopes for poisoning, returns an add, decline or sandbox verdict for a human. Never installs. Do not use to vet a skill or plugin (use skill-vet), to review first-party code (use review-hard or security-review)…

Mozurok/fhorja.dev · 0 tokens

screen-spec-fleet

Generate one spec document per screen in parallel from Figma frames, one worker per screen, merging SCREENMAP.md and routes.md from their partials; the orchestrator-workers variant of screen-spec. Use when the screen count is 6 or more, a Figma MCP is reachable, and foundations plus SCREENMAP exist. Do not use for a…

Mozurok/fhorja.dev · 113 tokens

image-to-spec

Generate a design-system spec from an image (screenshot, mockup, or app screen) when there is no Figma source: a component spec (--component) or screen spec (--screen), auto-detected. A gated --gameplay mode (off by default) derives a game MECHANICSSPEC.md from screenshots and playtest notes. Use when you have only an…

Mozurok/fhorja.dev · 0 tokens