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.
git clone --depth 1 https://github.com/marcusgoll/Spec-FlowWrote 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.
[](https://agentmods.dev/commands/marcusgoll/spec-flow/create-prompt)<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/create-prompt"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/create-prompt/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.
<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/create-prompt"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/create-prompt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.03181 |
| Opus 5.5 | $0.00008 | $0.01272 |
| Sonnet 5.5 | $0.00004 | $0.00636 |
| Haiku 4.5 | $0.00002 | $0.00318 |
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 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.
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` 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
-
Task complexity: Is this simple (single file, clear goal) or complex (multi-file, research needed, multiple steps)?
-
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?
-
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)
-
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")
-
Project context needs: Do I need to examine the codebase structure, dependencies, or existing patterns?
-
Optimal prompt depth: Should this be concise or comprehensive based on the task?
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.
- 2mo ago First seen · 385 lines · 19 tokens per session scan B b55e52e4c0cc
create-prompt is a command published in the GitHub repository marcusgoll/Spec-Flow (97 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 3,181 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
dare-llm-integration
Integração segura e eficiente com LLMs (Gemini, Claude, OpenAI, Ollama) em projetos DARE.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
audit-prompt
Evaluate an existing prompt for clarity, effectiveness, and edge cases.
a
Intercept Mode - Auto-improve and execute immediately.
rate-prompt
Rate a prompt file against the 100-point rubric and apply remediations to file.