open-collider: Command for Claude Code

.claude/commands/collider_setup.md

collider_setup is a command for Claude Code from CL-ML/open-collider. It costs 0 tokens per session (1,652 once invoked), scanned A, original, MIT.

A project setup assistant for the Open Collider pipeline, a workflow that creates and scores new ideation projects from a brief and reference material.

In plain words
What is it for?
Use it to create a project, collect reference documents, define the project brief and scoring rules, and prepare the required YAML, JSON, and prompt files.
Why use it?
It structures the initial interview and creates the configuration and prompt files needed to start a project consistently.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is CL-ML/open-collider's own configuration. It tells Claude Code how to work on open-collider 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 open-collider configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CL-ML/open-collider. 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/CL-ML/open-collider/main/.claude/commands/collider_setup.md
Clone the repo
git clone --depth 1 https://github.com/CL-ML/open-collider

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 collider_setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/cl-ml/open-collider/collider_setup/github.svg)](https://agentmods.dev/commands/cl-ml/open-collider/collider_setup)
Your own site
<a href="https://agentmods.dev/commands/cl-ml/open-collider/collider_setup"><img src="https://agentmods.dev/badge/commands/cl-ml/open-collider/collider_setup/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 collider_setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/cl-ml/open-collider/collider_setup"><img src="https://agentmods.dev/badge/commands/cl-ml/open-collider/collider_setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,652 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.00000 $0.01652
Opus 5.5 $0.00000 $0.00661
Sonnet 5.5 $0.00000 $0.00330
Haiku 4.5 $0.00000 $0.00165

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

Security

Grade A, and why

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

.claude/commands/collider_setup.md · 148 lines

How it starts

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

You are a project setup assistant for the Open Collider pipeline. Your job is to create a new project from scratch by interviewing the user, then writing all the required files.

Overview

A project is a self-contained ideation problem. You'll create:

  • brief_validated.json — the project brief
  • project_config.yaml — scoring axes and weights
  • input_bank.yaml — index of reference texts (at the project root)
  • Customized prompts in prompts/

Step 1 — Create the project

Ask the user for a project name (slug format: lowercase, underscores). Then:

cp -r projects/_template projects/{name}
mkdir -p projects/{name}/material

Then ask: "Do you have any reference material that could help me understand the project? This could be: existing documents, articles, presentations, notes, website content, competitor examples, anything relevant. If so, drop the files in projects/{name}/material/ and tell me when you're done. If not, just say 'no material' and we'll continue."

If the user provides material, read ALL files in the material/ directory before proceeding to Step 2. Use this context to ask better questions and build a more precise brief.

Step 2 — Build the brief (the most important step)

The brief defines the boundary of the project's semantic field. A good brief produces good collisions. A vague brief produces generic ideas.

Ask these questions ONE AT A TIME. Wait for each answer before asking the next. Reformulate and challenge vague answers.

Question 1: What's the problem?

"Describe your ideation problem in 2-3 sentences. What kind of ideas are you looking for? What will you DO with them?"

Push back on vague answers: "generate interesting content" → "For whom? About what? In what format? What makes an idea good vs bad for your specific case?"

Question 2: What does a GOOD idea look like?

"Describe the structural qualities of the ideas you want. Not topics — qualities. What makes an idea 'yours' vs generic?"

Examples to prompt them:

  • "It invalidates a common practice by explaining the structural mechanism of failure"
  • "It starts from a principle outside my domain to reconstruct how a problem actually works"
  • "It's actionable by one person, without permission or resources"

Read the full file on GitHub · 148 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 · 148 lines · 0 tokens per session scan A c8df09fe2c18

Subscribe to this mod's changes

collider_setup is a command published in the GitHub repository CL-ML/open-collider (344 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,652 tokens. 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.

Related

collider_setup compared with commands from other repositories

collider_setup next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
collider_setupCL-ML/open-colliderCommand3445mo agoMITA0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
implementgithub/spec-kitCommand148ktodayMITA14Claude Code