design-service

design-service is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 0 tokens per session (139 once invoked), scanned A, original, Apache-2.0.

A command for designing a backend service: a program that handles data and operations behind an app. It produces boundaries, data models, API endpoints, internal plans, communication methods, failure handling, and documentation.

In plain words
What is it for?
Use it to plan a service’s responsibilities, entities, API contract, internal components, communication with other services, and observability.
Why use it?
It turns a broad service idea into a clearer technical design before implementation. It also highlights that each service should own its data and that outside calls can fail.

Command

Part of the backend-architect plugin — 2 commands shipped together

About the project

Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.

rohitg00/awesome-claude-code-toolkit · 2,587 stars · on GitHub

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/design-service
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install backend-architect, the plugin that ships this one along with the rest of its 2 commands.

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-service

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/design-service.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/design-service)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/design-service"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/design-service.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 139 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00139
Opus 5 $0.00000 $0.00069
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

Measured 5d ago against content hash ddf87833ac29, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-service 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.

plugins/backend-architect/commands/design-service.md · 31 lines

What it actually says

Design a backend service architecture with clear boundaries, data models, and API contracts.

Steps

  1. Define the service scope:
  2. Design the data model:
  3. Design the API layer:
  4. Plan the service internals:
  5. Design inter-service communication:
  6. Plan for observability:
  7. Document the service contract.

Format

Service: <name>
Domain: <what it owns>
Entities: <data model summary>
API Endpoints: <list>

Rules

  • Each service should own its data; no shared databases.
  • Design for failure: every external call can fail.
  • Use interface segregation; expose only what consumers need.
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. 5d ago First seen · 31 lines · 0 tokens per session scan A ddf87833ac29

Subscribe to this mod's changes

design-service is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 139 tokens. 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.