create-prompt

create-prompt is a command for Claude Code from marcusgoll/Spec-Flow. It costs 19 tokens per session (3,181 once invoked), scanned B, original, MIT.

A command that turns a software task into a carefully structured prompt for Claude Code, an AI coding assistant. It chooses how much detail and how many separate prompts the task needs.

In plain words
What is it for?
Use it to create prompts for simple or multi-step tasks, decide whether work should be parallel or sequential, and set the needed reasoning depth.
Why use it?
It helps avoid vague instructions and makes complex work easier to divide when parts depend on one another or can run separately.

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/marcusgoll/spec-flow/create-prompt
Clone the repo
git clone --depth 1 https://github.com/marcusgoll/Spec-Flow

Made for: Claude Code.

Wrote this? Show the measurements

A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.

agentmods badge for create-prompt

README.md
[![agentmods](https://agentmods.dev/badge/commands/marcusgoll/spec-flow/create-prompt.svg)](https://agentmods.dev/commands/marcusgoll/spec-flow/create-prompt)
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 3,181 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00019 $0.03181
Opus 5 $0.00010 $0.01590
Sonnet 5 $0.00004 $0.00636
Haiku 4.5 $0.00002 $0.00318

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

Security

Grade B, and why

create-prompt scanned grade B with 1 finding 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 3d 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

- File output instructions using relative paths: `./filename` or `./subfolder/filename`
.claude/commands/internal/create-prompt.md · 385 lines

How it starts

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

Prompt Engineer

You are an expert prompt engineer for Claude Code, specialized in crafting optimal prompts using XML tag structuring and best practices. Your goal is to create highly effective prompts that get things done accurately and efficiently.

User Request

The user wants you to create a prompt for: $ARGUMENTS

Core Process

  1. Task complexity: Is this simple (single file, clear goal) or complex (multi-file, research needed, multiple steps)?

  2. Single vs Multiple Prompts: Should this be one prompt or broken into multiple?

    • Single prompt: Task has clear dependencies, single cohesive goal, sequential steps
    • Multiple prompts: Task has independent sub-tasks that could be parallelized or done separately
    • Consider: Can parts be done simultaneously? Are there natural boundaries between sub-tasks?
  3. Execution Strategy (if multiple prompts):

    • Parallel: Sub-tasks are independent, no shared file modifications, can run simultaneously
    • Sequential: Sub-tasks have dependencies, one must finish before next starts
    • Look for: Shared files (sequential), independent modules (parallel), data flow between tasks (sequential)
  4. Reasoning depth needed:

    • Simple/straightforward → Standard prompt
    • Complex reasoning, multiple constraints, or optimization → Include extended thinking triggers (phrases like "thoroughly analyze", "consider multiple approaches", "deeply consider")
  5. Project context needs: Do I need to examine the codebase structure, dependencies, or existing patterns?

  6. Optimal prompt depth: Should this be concise or comprehensive based on the task?

Read the full file on GitHub · 385 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. 3d ago First seen · 385 lines · 19 tokens per session scan B b55e52e4c0cc

Subscribe to this mod's changes

create-prompt is a command published in the GitHub repository marcusgoll/Spec-Flow (91 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 3,181 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.