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.
npx agentmods add commands/cakemail/cakemail-api-documentation-mcp/create-docgit clone --depth 1 https://github.com/cakemail/cakemail-api-documentation-mcpWhat 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 | $0.00000 | $0.00889 |
| Opus 5 | $0.00000 | $0.00445 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
create-doc 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 yesterday.
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.
This is a copy
97% identical to create-doc — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/create-doc Task
When this command is used, execute the following task:
Create Document from Template (YAML Driven)
⚠️ CRITICAL EXECUTION NOTICE ⚠️
THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL
When this task is invoked:
- DISABLE ALL EFFICIENCY OPTIMIZATIONS - This workflow requires full user interaction
- MANDATORY STEP-BY-STEP EXECUTION - Each section must be processed sequentially with user feedback
- ELICITATION IS REQUIRED - When
elicit: true, you MUST use the 1-9 format and wait for user response - NO SHORTCUTS ALLOWED - Complete documents cannot be created without following this workflow
VIOLATION INDICATOR: If you create a complete document without user interaction, you have violated this workflow.
Critical: Template Discovery
If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
CRITICAL: Mandatory Elicitation Format
When elicit: true, this is a HARD STOP requiring user interaction:
YOU MUST:
- Present section content
- Provide detailed rationale (explain trade-offs, assumptions, decisions made)
- STOP and present numbered options 1-9:
- Option 1: Always "Proceed to next section"
- Options 2-9: Select 8 methods from data/elicitation-methods
- End with: "Select 1-9 or just type your question/feedback:"
- WAIT FOR USER RESPONSE - Do not proceed until user selects option or provides feedback
WORKFLOW VIOLATION: Creating content for elicit=true sections without user interaction violates this task.
NEVER ask yes/no questions or use any other format.
Processing Flow
- Parse YAML template - Load template metadata and sections
- Set preferences - Show current mode (Interactive), confirm output file
- Process each section:
- Skip if condition unmet
- Check agent permissions (owner/editors) - note if section is restricted to specific agents
- Draft content using section instruction
- Present content + detailed rationale
- IF elicit: true → MANDATORY 1-9 options format
- Save to file if possible
- Continue until complete
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.
- yesterday First seen · 108 lines · 0 tokens per session scan A 5c754bff9346
create-doc is a command published in the GitHub repository cakemail/cakemail-api-documentation-mcp (0 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 889 tokens. A static security scan graded it A with 0 findings. It is 97% identical to create-doc, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.