design

design is a command for Claude Code from d-mariano/spicyclaude. It costs 15 tokens per session (340 once invoked), scanned A, original, MIT.

A command that chooses a technical-design workflow based on the codebase and the kind of task, such as building a new system or adding to an existing one.

In plain words
What is it for?
Use it to classify a design task, select the relevant workflow instructions, and begin the appropriate design phase after approval.
Why use it?
It helps select the right planning process before implementation and requires confirmation of that choice.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Good fit Use it to classify a design task, select the relevant workflow instructions, and begin the appropriate design phase after approval.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/d-mariano/spicyclaude/design
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/d-mariano/spicyclaude

Made for: Claude Code.

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 design

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/d-mariano/spicyclaude/design"><img src="https://agentmods.dev/badge/commands/d-mariano/spicyclaude/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 340 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.00015 $0.00340
Opus 5 $0.00008 $0.00170
Sonnet 5 $0.00003 $0.00068
Haiku 4.5 $0.00002 $0.00034

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

Security

Grade A, and why

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 9d 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.

commands/design.md · 24 lines

What it actually says

I need to create a technical design for the following task:

$ARGUMENTS

Before starting, determine the right workflow:

  1. Check if an existing codebase is present in the working directory. Look for package manifests, src directories, and code files.

  2. Classify the task:

    • Greenfield: No relevant codebase, or building an entirely new system/service → Read and follow .claude/skills/greenfield-design/SKILL.md
    • Feature Integration: Adding to an existing codebase, preserving existing patterns → Read and follow .claude/skills/feature-integration/SKILL.md
    • Greenfield + Refactor: Rebuilding a system from scratch with migration from the old → Read .claude/skills/greenfield-design/SKILL.md AND .claude/skills/refactor-modifier/SKILL.md, apply the modifier's additions at each phase
    • Integration + Refactor: Restructuring within an existing system → Read .claude/skills/feature-integration/SKILL.md AND .claude/skills/refactor-modifier/SKILL.md, apply the modifier's additions at each phase
  3. Present your classification to me with reasoning. Ask me to confirm or override before proceeding.

  4. Once confirmed, execute the selected workflow from Phase 1, pausing after each phase for my review.

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. 9d ago First seen · 24 lines · 15 tokens per session scan A 22d569bc8703

Subscribe to this mod's changes

design is a command published in the GitHub repository d-mariano/spicyclaude (5 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 340 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.