create-command

An interactive wizard for creating a new slash command from scratch. It gathers the command's name, category, purpose, and required tools before creating its command file.

In plain words
What is it for?
Use it to create commands for founder-os categories such as queues, founder tools, team management, or configuration, with access to the tools the command needs.
Why use it?
It provides a structured way to define commands instead of having to remember the expected categories, fields, and file location.

Command for Claude Code

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.

agentmods
npx agentmods add commands/cloudrepo-io/founder-os/create-command
Clone the repo
git clone --depth 1 https://github.com/cloudrepo-io/founder-os

Made for: Claude Code.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 761 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00007 $0.00761
Opus 5 $0.00003 $0.00380
Sonnet 5 $0.00001 $0.00152
Haiku 4.5 $0.00001 $0.00076

Measured 2d ago against content hash 6c9088f92ecf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-command 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 2d 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/create-command.md · 115 lines

How it starts

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

Create Command Wizard

Interactively create a new slash command for your founder-os instance.

Arguments

  • $ARGUMENTS - (Optional) Name or description of the command to create

Process

Step 1: Command Identity

Ask the user (or derive from arguments):

  • Command name: What should the command be called? (e.g., deploy, audit, sprint-plan)
  • Category: Where should it live?

Use AskUserQuestion:

  • Question: "What category should this command belong to?"
  • Options:
    • "queue" - Work queue management
    • "founder" - Founder tools
    • "team" - Team management
    • "config" - Configuration
    • (Other will be entered manually)

The command file will be created at .claude/commands/{category}/{name}.md.

Step 2: Command Purpose

Ask: "What should this command do? Describe in 1-2 sentences."

Record as the description in the frontmatter.

Step 3: Tool Requirements

Use AskUserQuestion with multiSelect:

  • Question: "What tools does this command need access to?"
  • Options:
    • "Read" - Read files from the filesystem
    • "Write, Edit" - Create and modify files
    • "Bash" - Run shell commands
    • "Task, Glob, Grep" - Search codebase and spawn subagents
    • "AskUserQuestion" - Interactive prompts to the user

Step 4: Agent Assignment

Use AskUserQuestion:

  • Question: "Which agent type should primarily use this command?"
  • Options:
    • "Any agent" - No specific owner
    • "staff-software-architect" - Architecture and design
    • "staff-product-manager" - Product decisions
    • "staff-engineer" - Implementation

Step 5: Generate Command

Create the command file with this structure:

---
description: {description from step 2}
allowed-tools: {tools from step 3}
---

# {Command Title}

{Description of what this command does.}

## Arguments

- `$ARGUMENTS` - {describe expected arguments}

## Process

1. {Step 1 - what to do first}

2. {Step 2 - main action}

3. {Step 3 - verification/output}

## Output

{Describe what the command reports when done}

Read the full file on GitHub · 115 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. 2d ago First seen · 115 lines · 7 tokens per session scan A 6c9088f92ecf

Subscribe to this mod's changes

create-command is a command published in the GitHub repository cloudrepo-io/founder-os (19 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 761 once invoked, about $0.0000 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-08-30.