swarm-design-deep

swarm-design-deep is a skill for Claude Code, Codex from AnmarHani/SwarmVault. It costs 94 tokens per session (1,770 once invoked), scanned A, original, MIT.

A detailed software-design workflow in which the developer chooses each approach before implementation begins. It turns approved designs into pseudocode, algorithms, rules that must always hold, sequence diagrams, and test examples.

In plain words
What is it for?
Use it when you need careful control over system design, especially for complex behavior where implementation should follow a fully worked-out plan. It requires validated software requirements.
Why use it?
It helps developers understand and own the system instead of receiving an architecture they cannot easily explain or maintain.

Skill for Claude CodeCodex

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

Good fit Use it when you need careful control over system design, especially for complex behavior where implementation should follow a fully worked-out plan. It requires validated software requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anmarhani/swarmvault/swarm-design-deep
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 AnmarHani/SwarmVault --skill swarm-design-deep
Clone the repo
git clone --depth 1 https://github.com/AnmarHani/SwarmVault

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 swarm-design-deep

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-design-deep"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-design-deep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,770 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.00094 $0.01770
Opus 5 $0.00047 $0.00885
Sonnet 5 $0.00019 $0.00354
Haiku 4.5 $0.00009 $0.00177

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

Security

Grade A, and why

swarm-design-deep 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.

skills/swarm-design-deep/SKILL.md · 135 lines

How it starts

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

swarm-design-deep — the developer-driven design lane

Gate: requires a validated SRS. This lane replaces swarm-design for the phase — do not run both; one skill owns the design artifacts.

The standard lane (swarm-design) is agent-driven: it proposes an architecture and the user validates it. That is the right trade for most projects. This lane exists for the other case — a developer who must hold the system in their head afterwards. It is slower and costs more tokens on purpose, and it pays for itself only if implementation comes out mechanical.

The contract

Treat the design session as the agent, and apply six of the 12 factors to it:

applied here
8 own your control flow The user decides what is designed next. Never advance the unit list yourself.
7 contact humans with tool calls Every unresolved choice is an explicit question. No assumption reaches the doc silently.
3 own your context window Design lives in per-unit files, not the transcript. This is what makes the depth affordable.
6 launch/pause/resume One unit per session, closed and dropped. A cold session resumes from the unit table.
12 stateless reducer Each session = (files so far + one decision) → updated files.
10 small, focused agents One unit designed to the bottom beats the whole system designed halfway.

Awareness is caused by producing, not by reading. Forty pages of excellent design gets a rubber stamp. The commit step below is the whole point of the lane; without it this is just swarm-design with more words.

Setup — the design profile (ask once)

Write docs/design/profile.md, then never ask again:

  • design language — what algorithms and signatures are written in. Independent of the implementation language: designing in Java and building in Python is normal. Language-neutral pseudocode is a valid answer. Say this out loud when asking, because users assume it's the build language.
  • granularity — what one unit is here (module / service / endpoint / algorithm).
  • diagram formats — see references/diagrams.md.
  • standing depth override, if any.

Read the full file on GitHub · 135 lines

Files

What ships with it

2 files 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. 9d ago First seen · 135 lines · 0 tokens per session scan A d9f6444ed83a

Subscribe to this mod's changes

swarm-design-deep is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,770 once invoked, about $0.0005 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.