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.
git clone --depth 1 https://github.com/athola/claude-night-marketWrote 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.
[](https://agentmods.dev/commands/athola/claude-night-market/blueprint)<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.
<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>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.
| Model | Per session | Once 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 |
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.
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:specifyfirst) - Still defining requirements (complete specification phase)
- Ready to execute existing plan (use
/attune:executeinstead) - 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
- Loads specification from specify phase
- Invokes planning skill with superpowers integration
- Designs system architecture (components, interfaces, data flow)
- Breaks down into tasks with dependencies and estimates
- 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)
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.
- 7d ago First seen · 456 lines · 21 tokens per session scan A 07397626a8af
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.
Other commands, from other repositories
contact-upsert
Create or update a contact, optionally assign to groups.
github-issue-fix
This is a detailed way you can analyze the GitHub issues and let Claude handle them in best possible way.
spec
A requirements-planning command for OpenSpec, a tool that records software changes as proposals, specification updates, and task lists. It clarifies the request, challenges risky assumptions, and pauses for approval before implementation.
start
Analyze this project and build a GoalT goal tree for it, linking real files and backend artifacts to each goal.
features:add
(Features) Add a new feature to a specific phase.
features:status
(Features) Show implementation status by phase.