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/cakemail/cakemail-api-documentation-mcpWrote 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/cakemail/cakemail-api-documentation-mcp/brownfield-create-story)<a href="https://agentmods.dev/commands/cakemail/cakemail-api-documentation-mcp/brownfield-create-story"><img src="https://agentmods.dev/badge/commands/cakemail/cakemail-api-documentation-mcp/brownfield-create-story.svg" alt="Measured on agentmods" 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.00000 | $0.00937 |
| Opus 5 | $0.00000 | $0.00468 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
brownfield-create-story 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 7d 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.
This is a copy
97% identical to brownfield-create-story — 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brownfield-create-story Task
When this command is used, execute the following task:
Create Brownfield Story Task
Purpose
Create a single user story for very small brownfield enhancements that can be completed in one focused development session. This task is for minimal additions or bug fixes that require existing system integration awareness.
When to Use This Task
Use this task when:
- The enhancement can be completed in a single story
- No new architecture or significant design is required
- The change follows existing patterns exactly
- Integration is straightforward with minimal risk
- Change is isolated with clear boundaries
Use brownfield-create-epic when:
- The enhancement requires 2-3 coordinated stories
- Some design work is needed
- Multiple integration points are involved
Use the full brownfield PRD/Architecture process when:
- The enhancement requires multiple coordinated stories
- Architectural planning is needed
- Significant integration work is required
Instructions
1. Quick Project Assessment
Gather minimal but essential context about the existing project:
Current System Context:
- Relevant existing functionality identified
- Technology stack for this area noted
- Integration point(s) clearly understood
- Existing patterns for similar work identified
Change Scope:
- Specific change clearly defined
- Impact boundaries identified
- Success criteria established
2. Story Creation
Create a single focused story following this structure:
Story Title
{{Specific Enhancement}} - Brownfield Addition
User Story
As a {{user type}}, I want {{specific action/capability}}, So that {{clear benefit/value}}.
Story Context
Existing System Integration:
- Integrates with: {{existing component/system}}
- Technology: {{relevant tech stack}}
- Follows pattern: {{existing pattern to follow}}
- Touch points: {{specific integration points}}
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.
- 7d ago First seen · 154 lines · 0 tokens per session scan A 82f80d5a5eec
brownfield-create-story 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 937 tokens. A static security scan graded it A with 0 findings. It is 97% identical to brownfield-create-story, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.