blueprint

blueprint is a command for Claude Code from athola/claude-night-market. It costs 21 tokens per session (2,963 once invoked), scanned A, original, MIT.

A planning command that turns a specification into an implementation roadmap with architecture, component details, data flow, and tasks arranged by dependency.

In plain words
What is it for?
Use it to design a system from its requirements, define component interfaces, estimate work, plan sprints, and create an executable task list.
Why use it?
It breaks a defined project into concrete pieces so developers know what to build and in what order.

Command for Claude Code

Written for Claude Code: Claude Code plugin machinery.

Part of the attune plugin — 14 skills, 11 commands, 2 agents shipped together

Good fit Use it to design a system from its requirements, define component interfaces, estimate work, plan sprints, and create an executable task list.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/athola/claude-night-market/blueprint
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/athola/claude-night-market

Made for: Claude Code.

Or install attune, the plugin that ships this one along with the rest of its 14 skills, 11 commands, 2 agents.

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 blueprint

README.md
[![agentmods](https://agentmods.dev/badge/commands/athola/claude-night-market/blueprint/github.svg)](https://agentmods.dev/commands/athola/claude-night-market/blueprint)
Your own site
<a href="https://agentmods.dev/commands/athola/claude-night-market/blueprint"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/blueprint/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 blueprint

Your own site · 80×15
<a href="https://agentmods.dev/commands/athola/claude-night-market/blueprint"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/blueprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,963 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.00021 $0.02963
Opus 5 $0.00010 $0.01482
Sonnet 5 $0.00004 $0.00593
Haiku 4.5 $0.00002 $0.00296

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

Security

Grade A, and why

blueprint 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 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.

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/attune/commands/blueprint.md · 456 lines

How it starts

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

Attune Plan Command

Transform specifications into executable implementation plans with system architecture, component design, and dependency-ordered task breakdown.

When To Use

Use this command when you need to:

  • Convert specification into implementation plan
  • Design system architecture from requirements
  • Break down work into dependency-ordered tasks
  • Estimate effort and plan sprints
  • Define component interfaces and data flow
  • Create concrete roadmap for execution

When NOT To Use

Avoid this command if:

  • No specification exists yet (use /attune:specify first)
  • Still defining requirements (complete specification phase)
  • Ready to execute existing plan (use /attune:execute instead)
  • Adjusting running project (update plan incrementally)

Usage

# Create plan from specification
/attune:blueprint

# Plan with custom input
/attune:blueprint --input docs/specification.md

# Focus on specific component
/attune:blueprint --component "authentication"

What This Command Does

  1. Loads specification from specify phase
  2. Invokes planning skill with superpowers integration
  3. Designs system architecture (components, interfaces, data flow)
  4. Breaks down into tasks with dependencies and estimates
  5. Produces implementation plan for execution phase

Integration with Superpowers

When superpowers plugin is available:

  • Uses Skill(superpowers:writing-plans) for structured planning
  • Applies dependency analysis
  • Creates checkpoint-based execution flow

Without superpowers:

  • Falls back to attune's native planning skill
  • Provides similar step-by-step approach
  • Documents tasks systematically

Workflow

# 1. Invoke planning skill
Skill(attune:project-planning)

# 2. Design architecture:
#    - System components
#    - Component interfaces
#    - Data flow diagrams
#    - Technology selections

# 3. Break down into tasks:
#    - Development tasks with dependencies
#    - Testing tasks
#    - Deployment tasks
#    - Documentation tasks

# 4. Generate implementation plan
#    - Saved to docs/implementation-plan.md
#    - Includes architecture + task breakdown

# 5. Workflow auto-continues (see below)

Read the full file on GitHub · 456 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. 7d ago First seen · 456 lines · 21 tokens per session scan A 07397626a8af

Subscribe to this mod's changes

blueprint is a command published in the GitHub repository athola/claude-night-market (337 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,963 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-09-03.