sd

sd is a skill for Claude Code from Everyone-Needs-A-Copilot/claude-copilot. It costs 51 tokens per session (1,037 once invoked), scanned A, original, MIT.

A service-design method for shaping a software service before screens or code are created. It maps what users do, the behind-the-scenes work and systems involved, handoffs between stages, and what happens when something fails.

In plain words
What is it for?
It is for defining user outcomes, mapping journeys and recovery paths, identifying assumptions and service constraints, comparing service concepts, and handing clearer requirements to design or engineering.
Why use it?
It helps teams solve the real user or business problem instead of jumping straight to a feature. It also exposes operational constraints and broken handoffs that a screen-by-screen design may miss.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-copilot plugin — 73 skills, 18 commands, 16 agents, 6 hooks shipped together

Good fit It is for defining user outcomes, mapping journeys and recovery paths, identifying assumptions and service constraints, comparing service concepts, and handing clearer requirements to design or engineering.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/everyone-needs-a-copilot/claude-copilot/sd
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.

Any agent
npx skills add Everyone-Needs-A-Copilot/claude-copilot --skill sd
Clone the repo
git clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilot

Made for: Claude Code.

Or install claude-copilot, the plugin that ships this one along with the rest of its 73 skills, 18 commands, 16 agents, 6 hooks.

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 sd

README.md
[![agentmods](https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/sd/github.svg)](https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/sd)
Your own site
<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/sd"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/sd/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 sd

Your own site · 80×15
<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/sd"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/sd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,037 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.00051 $0.01037
Opus 5.5 $0.00020 $0.00415
Sonnet 5.5 $0.00010 $0.00207
Haiku 4.5 $0.00005 $0.00104

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

Security

Grade A, and why

sd 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 6d 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/codex-copilot/skills/sd/SKILL.md · 91 lines

How it starts

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

Service Designer

Use this skill to shape software as a service experience before screens or code.

Operating Lens

  • Question the brief before solving it.
  • Frame the job to be done and the forces acting on behavior.
  • Map frontstage user actions, backstage systems, support processes, and failure recovery.
  • Identify transitions between stages; most product experience breaks at handoffs.
  • Produce options with tradeoffs instead of a single assumed solution.

Taste Applicability

Read only taste rules whose lens includes this specialist and whose Applies: scope matches this project or is personal; do not import another project's rule. Project constraints and repository instructions outrank personal taste. State which rule was set aside on conflict.

Workflow

  1. Read 08-taste/INDEX.md from the nearest paths.knowledge_repo entry that has one — resolved tensions from this owner's own feedback, personal tier only, empty until earned. Apply the reasoning, not the example; when a rule does not fit, say so rather than forcing it.

  2. Restate the real user or business outcome.

  3. Name assumptions and evidence. If evidence is missing, label hypotheses.

  4. Map the current or intended journey, including failure and recovery paths.

  5. Identify service constraints: people, process, data, systems, policies, and operational load.

  6. Define the preferred service concept and rejected alternatives.

  7. Hand off to $uxd for interaction design or $ta for technical decomposition.

Success Criteria

  • The user outcome and service boundary are explicit.
  • Failure and recovery paths are included.
  • Frontstage and backstage responsibilities are separated.
  • The recommendation names rejected alternatives.
  • A specification work product is stored when tc context exists.

Iteration Loop

Iterate until the service concept has a clear user outcome, operational owner, failure path, and next specialist handoff. If evidence is missing, label assumptions instead of overclaiming certainty.

Read the full file on GitHub · 91 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. 6d ago Changed 7f5dbb956f97
  2. 7d ago Changed · +7 lines 79d0c2aac00e
  3. 1mo ago Changed · +16 lines c9b5f5c56f2b
  4. 1mo ago First seen · 68 lines · 51 tokens per session scan A 179c8213005f

Subscribe to this mod's changes

sd is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,037 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-09-04.

Related

Other skills, from other repositories

DesignSystemArchitect

Complete design system intelligence — component library design, design tokens, documentation, adoption strategy, governance, versioning, and building a design system that scales with your product.

vignesh2027/Claude-Agentic-Skills2.0-version · 36 tokens

UserResearchOS

Complete user research intelligence — research planning, interview mastery, usability testing, survey design, Jobs-to-be-Done framework, synthesis, and turning user insights into product decisions.

vignesh2027/Claude-Agentic-Skills2.0-version · 37 tokens

onboarding-designer

Activates OnboardingDesigner for user and customer onboarding experience design. Use when you need to design a product onboarding flow that minimizes time-to-value, create an in-app onboarding checklist or tour, design a customer onboarding sequence for B2B SaaS, build an email onboarding drip campaign, or analyze…

vignesh2027/Claude-Agentic-Skills2.0-version · 72 tokens

multi-modal-analyst

Activates MultiModalAnalyst for analyzing images, charts, diagrams, screenshots, and visual documents alongside text. Use when you need to extract data from chart images, analyze UI screenshots for UX issues, interpret architectural diagrams, read scanned documents, analyze product mockups, or process any visual input…

vignesh2027/Claude-Agentic-Skills2.0-version · 71 tokens

ui-ux-designer

Activates UI-UX-Designer for user experience design, interface critique, and accessibility review. Use when you need user flow mapping and friction identification, wireframe critique and design improvement recommendations, accessibility audit against WCAG 2.1 AA standards, design system component specification, or…

vignesh2027/Claude-Agentic-Skills2.0-version · 69 tokens

anatomy

Explain an idea as an interactive isometric machine figure.

NousResearch/hermes-agent · 15 tokens