concept:blackbox

concept:blackbox is a command for Claude Code from ddunnock/claude-plugins. It costs 28 tokens per session (1,333 once invoked), scanned A, original, MIT.

A command for describing a concept as connected functional blocks, relationships, guiding principles, and simple text diagrams. It explains what the concept should do without specifying implementation details.

In plain words
What is it for?
Use it after the problem statement is complete to outline possible architectures, their responsibilities, how their parts interact, and the capabilities they could provide.
Why use it?
It provides a shared high-level view before technical design begins. Comparing distinct functional approaches can reveal trade-offs without prematurely choosing tools or platforms.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the concept-dev plugin — 1 skill, 9 commands, 7 agents shipped together

Good fit Use it after the problem statement is complete to outline possible architectures, their responsibilities, how their parts interact, and the capabilities they could provide.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ddunnock/claude-plugins
Claude Code
/plugin install concept-dev

Made for: Claude Code.

Or install concept-dev, the plugin that ships this one along with the rest of its 1 skill, 9 commands, 7 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 concept:blackbox

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/ddunnock/claude-plugins/concept.blackbox"><img src="https://agentmods.dev/badge/commands/ddunnock/claude-plugins/concept.blackbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,333 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.00028 $0.01333
Opus 5.5 $0.00011 $0.00533
Sonnet 5.5 $0.00006 $0.00267
Haiku 4.5 $0.00003 $0.00133

Measured 1mo ago against content hash 13af26ae7dbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

concept:blackbox 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 1mo 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/concept-dev/commands/concept.blackbox.md · 204 lines

How it starts

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

/concept:blackbox

Phase 3 of concept development: black-box architecture.

Prerequisites

Run the prerequisite gate check:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --state .concept-dev/state.json check-gate blackbox

If this exits non-zero, stop and tell the user to complete the previous phase first.

Then load context:

  • python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --state .concept-dev/state.json show
  • Read: .concept-dev/PROBLEM-STATEMENT.md

Procedure

Step 1: Set Phase

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --state .concept-dev/state.json set-phase blackbox

Step 2: Context Loading

Read .concept-dev/PROBLEM-STATEMENT.md and present:

===================================================================
BLACK-BOX ARCHITECTURE
===================================================================

Problem: [1-2 sentence summary]
Scope: [IN scope summary]
Key Constraints: [List]

I'll propose 2-3 high-level approaches to solving this problem.
Each approach describes WHAT the concept does at a functional level
— not HOW it's implemented.

For each approach, I'll describe:
  - Functional blocks and their responsibilities
  - Relationships between blocks
  - Guiding principles
  - Capabilities this architecture enables
  - Trade-offs

===================================================================

Step 3: Propose Approaches

Use the concept-architect agent. Present 2-3 distinct architectural approaches:

===================================================================
APPROACH 1: [Name]
===================================================================

CONCEPT: [2-3 sentence description]

FUNCTIONAL BLOCKS:
  [Block A] — [What it does, not how]
  [Block B] — [What it does, not how]
  [Block C] — [What it does, not how]

RELATIONSHIPS:
  [Block A] → [Block B]: [What flows between them]
  [Block B] ↔ [Block C]: [Bidirectional relationship]

PRINCIPLES:
  1. [Guiding principle]
  2. [Guiding principle]

ENABLES:
  - [Capability this approach uniquely enables]
  - [Capability]

TRADE-OFFS:
  + [Advantage]
  + [Advantage]
  - [Disadvantage]
  - [Disadvantage]

===================================================================
APPROACH 2: [Name]
===================================================================
[Same structure]

===================================================================
APPROACH 3: [Name]
===================================================================
[Same structure]

Read the full file on GitHub · 204 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. 1mo ago First seen · 204 lines · 28 tokens per session scan A 13af26ae7dbd

Subscribe to this mod's changes

concept:blackbox is a command published in the GitHub repository ddunnock/claude-plugins (14 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 1,333 once invoked, about $0.0001 per session on Opus 5.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-30.