Create Design Document

Create Design Document is a skill for Claude Code, Codex from AmariahAK/atlarix-skills. It costs 3 tokens per session (992 once invoked), scanned B, a copy of create-design-document, Apache-2.0.

A prompt pattern for writing a clear technical design document about a software, cloud, or cybersecurity system.

In plain words
What is it for?
Use it to document proposed systems and components, including their architecture and security considerations.
Why use it?
It helps organize an idea into an understandable description of its components, structure, and technical decisions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to document proposed systems and components, including their architecture and security considerations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amariahak/atlarix-skills/fabric-create-design-document
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 AmariahAK/atlarix-skills --skill fabric-create-design-document
Clone the repo
git clone --depth 1 https://github.com/AmariahAK/atlarix-skills

Made for: Claude Code, Codex.

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 Create Design Document

README.md
[![agentmods](https://agentmods.dev/badge/skills/amariahak/atlarix-skills/fabric-create-design-document/github.svg)](https://agentmods.dev/skills/amariahak/atlarix-skills/fabric-create-design-document)
Your own site
<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/fabric-create-design-document"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/fabric-create-design-document/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 Create Design Document

Your own site · 80×15
<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/fabric-create-design-document"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/fabric-create-design-document.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 992 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod 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.00003 $0.00992
Opus 5 $0.00002 $0.00496
Sonnet 5 $0.00001 $0.00198
Haiku 4.5 $0.00000 $0.00099

Measured 7d ago against content hash 5a2c01866e68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

Create Design Document scanned grade B with 1 finding 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 7d 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

# OUTPUT INSTRUCTIONS
Origin

This is a copy

88% identical to create-design-document — 37 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/fabric-create-design-document/SKILL.md · 71 lines

How it starts

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

Create Design Document

When to use this skill

You are an expert in software, cloud and cybersecurity architecture. You specialize in creating clear, well written design documents of systems and components.

Source

Synced from https://github.com/danielmiessler/fabric/tree/main/data/patterns/create_design_document/system.md.

IDENTITY and PURPOSE

You are an expert in software, cloud and cybersecurity architecture. You specialize in creating clear, well written design documents of systems and components.

GOAL

Given a description of idea or system, provide a well written, detailed design document.

STEPS

  • Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.

  • Think deeply about the nature and meaning of the input for 28 hours and 12 minutes.

  • Create a virtual whiteboard in you mind and map out all the important concepts, points, ideas, facts, and other information contained in the input.

  • Fully understand the The C4 model for visualising software architecture.

  • Appreciate the fact that each company is different. Fresh startup can have bigger risk appetite then already established Fortune 500 company.

  • Take the input provided and create a section called BUSINESS POSTURE, determine what are business priorities and goals that idea or system is trying to solve. Give most important business risks that need to be addressed based on priorities and goals.

  • Under that, create a section called SECURITY POSTURE, identify and list all existing security controls, and accepted risks for system. Focus on secure software development lifecycle and deployment model. Prefix security controls with 'security control', accepted risk with 'accepted risk'. Withing this section provide list of recommended security controls, that you think are high priority to implement and wasn't mention in input. Under that but still in SECURITY POSTURE section provide list of security requirements that are important for idea or system in question.

Read the full file on GitHub · 71 lines

Files

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.

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. 7d ago First seen · 71 lines · 3 tokens per session scan B 5a2c01866e68

Subscribe to this mod's changes

Create Design Document is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3 tokens to every session and 992 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). It is 88% identical to create-design-document, differing in 37 lines, and is treated as a copy.

Related

Other skills, from other repositories

app-ui-design

Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.

majiayu000/spellbook · 54 tokens

idea-team

A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.

majiayu000/spellbook · 182 tokens

capability-distill

A workflow for extracting specific decision rules from approved expert-model interviews or real task records and packaging them for skill review.

majiayu000/spellbook · 136 tokens

project-health-auditor

Comprehensive codebase health analysis. Use when reviewing code quality, identifying technical debt, checking dependencies, or assessing project structure.

majiayu000/spellbook · 31 tokens

skill-lifeguard

Use when a skill is brittle, drifting, repeatedly failing, or needs a Reliable Skill Contract. Trigger for phrases like skill lifeguard, reliable skill, self-maintaining skill, negative examples, verification checkpoints, drift signals, replay hooks, or failure log to skill patch. Audits or patches skills so…

majiayu000/spellbook · 92 tokens

review-gate

Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…

majiayu000/spellbook · 95 tokens