cassini-workshop: Command for Claude Code

.claude/commands/explore.md

explore is a command for Claude Code from robconery/cassini-workshop. It costs 19 tokens per session (602 once invoked), scanned A, a copy of explore, MIT.

A guided interview command for defining a software idea before choosing its technical solution. It records the problem, intended users, scope, success measures, and unknowns in docs/PROJECT.md.

In plain words
What is it for?
Exploring who has a problem, why it matters now, what belongs in the project, what does not, and what still needs to be learned.
Why use it?
It turns an incomplete idea into a clearer project brief and helps prevent architecture decisions from being made before the problem is understood.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md; names the AskUserQuestion tool.

This is robconery/cassini-workshop's own configuration. It tells Claude Code how to work on cassini-workshop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cassini-workshop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to robconery/cassini-workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/robconery/cassini-workshop/main/.claude/commands/explore.md
Clone the repo
git clone --depth 1 https://github.com/robconery/cassini-workshop

Made for: Claude Code.

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 explore

README.md
[![agentmods](https://agentmods.dev/badge/commands/robconery/cassini-workshop/explore/github.svg)](https://agentmods.dev/commands/robconery/cassini-workshop/explore)
Your own site
<a href="https://agentmods.dev/commands/robconery/cassini-workshop/explore"><img src="https://agentmods.dev/badge/commands/robconery/cassini-workshop/explore/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 explore

Your own site · 80×15
<a href="https://agentmods.dev/commands/robconery/cassini-workshop/explore"><img src="https://agentmods.dev/badge/commands/robconery/cassini-workshop/explore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 602 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 100% 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.00019 $0.00602
Opus 5.5 $0.00008 $0.00241
Sonnet 5.5 $0.00004 $0.00120
Haiku 4.5 $0.00002 $0.00060

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

Security

Grade A, and why

explore 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 2mo 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.

Origin

This is a copy

100% identical to explore — 0 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.

.claude/commands/explore.md · 61 lines

How it starts

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

explore

Think through an idea with me. This is a problem-space interview, not a solution. By the end, docs/PROJECT.md says what we're building and why, honestly including what we don't know yet.

IMPORTANT: ask if there's an existing spec written anywhere. If so, ask for it and improve on it, otherwise proceed as if nothing existed.

Scope

  • IN: the problem, the user, the why-now, in/out scope, success, unknowns, light research where a fact is needed to proceed.
  • OUT: architecture, schema, platform, tech choices — all /design. If a solution idea comes up, park it under "Open questions", don't decide it.

Preflight

  1. Read docs/PROJECT.md if it exists. Summarize current state in 1–2 lines ("scope defined, no success metric yet"). Re-entrant: refine, don't restart.
  2. Read CLAUDE.md and docs/MEMORY.md for prior context.

Interview

Up to ~10 questions, adaptive — only ask what's missing or unresolved. Batch them (AskUserQuestion, 4 at a time → 2–3 rounds, not an interrogation). Question bank, in priority order:

  1. What problem, concretely? What happens today without it?
  2. Who is it for? Who is not?
  3. Why now / why worth doing?
  4. What's explicitly out of scope?
  5. What does success look like — observable, ideally measurable?
  6. Hard constraints (time, money, platform, must/can't use)?
  7. What's the riskiest unknown?
  8. What's the smallest version that's still worth shipping?
  9. Any prior art or existing thing this replaces?
  10. What would make you kill this?

Do targeted research only when an answer hinges on a fact you can check.

Produce

  • docs/PROJECT.md (owned here): Problem, Who it's for, Goals, Success, Scope (in/out), Constraints, Open questions, Riskiest unknowns. Mark unresolved items TODO rather than guessing.
  • CLAUDE.md: fill the basics that surfaced (domain, one-line purpose). Update only — /init owns the file.
  • docs/MEMORY.md: append a dated entry for each decision actually made here (scope cut, killed alternative, etc.). One line each, with the why.

Read the full file on GitHub · 61 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. 2mo ago First seen · 61 lines · 19 tokens per session scan A 3b1a72a79c87

Subscribe to this mod's changes

explore is a command published in the GitHub repository robconery/cassini-workshop (1 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 602 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to explore, differing in 0 lines, and is treated as a copy.