agentmods.dev

create-command

create-command is a command for Claude Code from crathgeb/claude-code-plugins. It costs 10 tokens per session (3,327 once invoked), scanned A, original, MIT.

A guided command for creating a slash command, which is a reusable instruction started with a slash in Claude Code plugins.

In plain words
What is it for?
Use it to design commands for tasks such as creating features, scaffolding components, or running Git workflows.
Why use it?
It helps define the command's purpose, arguments, tool limits, context, and place in a larger workflow.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool; mentions Claude Code.

Part of the plugin-builder plugin — 3 commands, 2 agents shipped together

not rated 2repo 1y ago A scan 10 tokens original MIT

Good fit Use it to design commands for tasks such as creating features, scaffolding components, or running Git workflows.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/crathgeb/claude-code-plugins/create-command
View source ↗ crathgeb/claude-code-plugins
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.

Clone the repo
git clone --depth 1 https://github.com/crathgeb/claude-code-plugins

Made for: Claude Code.

Or install plugin-builder, the plugin that ships this one along with the rest of its 3 commands, 2 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 create-command

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/crathgeb/claude-code-plugins/create-command"><img src="https://agentmods.dev/badge/commands/crathgeb/claude-code-plugins/create-command.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,327 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.00010 $0.03327
Opus 5.5 $0.00004 $0.01331
Sonnet 5.5 $0.00002 $0.00665
Haiku 4.5 $0.00001 $0.00333

Measured 2mo ago against content hash 09b95af93b50, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugins/plugin-builder/commands/create-command.md · 715 lines

How it starts

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

Slash Command Builder

You are an expert in building Claude Code slash commands. Guide users through creating well-structured, constrained commands that follow best practices.

User request: $ARGUMENTS

Phase 1: Command Requirements

Step 1.1: Gather Information

If not provided, ask:

Essential:

  • Command name? (use dash-case: create-feature, run-tests)
  • What does this command do? (one-sentence purpose)
  • What arguments does it accept?

Optional:

  • Should this command be constrained to specific tools? (e.g., only git commands)
  • Does this command need inline context? (e.g., !git status output)
  • Is this command part of a larger workflow?

Step 1.2: Analyze Similar Commands

Search for similar commands to learn patterns. Consider:

Workflow Commands (multi-phase processes):

  • feature-dev - 7-phase feature development
  • create-component - Component scaffolding
  • Pattern: Discovery ->†-> Planning ->†-> Approval ->†-> Implementation ->†-> Documentation

Git Commands (version control):

  • commit - Create commits with smart messages
  • commit-push-pr - Full workflow from commit to PR
  • clean_gone - Clean up deleted branches
  • Pattern: Git operations with strict tool constraints

Interactive Commands (user guidance):

  • new-sdk-app - Interactive app creation wizard
  • Pattern: Ask questions ->†-> Validate ->†-> Execute

Analysis Commands (code review):

  • Component verification, pattern checking
  • Pattern: Analyze -> Report findings -> Optional fixes

Describe 1-2 relevant examples.

Phase 2: Command Design

Step 2.1: Choose Command Pattern

Based on requirements, select a pattern:

Pattern A: Simple Command

  • Single-phase execution
  • Minimal user interaction
  • Example: Clean up branches, format code

Pattern B: Workflow Command

  • Multiple phases (Discovery -> Planning -> Execution)
  • User approval gates
  • Todo list tracking
  • Example: Feature development, component creation

Pattern C: Interactive Command

Read the full file on GitHub · 715 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 · 715 lines · 10 tokens per session scan A 09b95af93b50

Subscribe to this mod's changes

create-command is a command published in the GitHub repository crathgeb/claude-code-plugins (2 stars, last pushed 1y ago), licensed MIT. It adds 10 tokens to every session and 3,327 once invoked, about $0.0000 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-31.

Building agents
Related

create-command compared with commands from other repositories

create-command next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-commandcrathgeb/claude-code-pluginsCommand21y agoMITA10Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
speckit.bug.testgithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code