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/brownfield-create-epicgit 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-epic)<a href="https://agentmods.dev/commands/cakemail/cakemail-api-documentation-mcp/brownfield-create-epic"><img src="https://agentmods.dev/badge/commands/cakemail/cakemail-api-documentation-mcp/brownfield-create-epic.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.00991 |
| Opus 5 | $0.00000 | $0.00495 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
brownfield-create-epic 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 5d 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
98% identical to brownfield-create-epic — 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/brownfield-create-epic Task
When this command is used, execute the following task:
Create Brownfield Epic Task
Purpose
Create a single epic for smaller brownfield enhancements that don't require the full PRD and Architecture documentation process. This task is for isolated features or modifications that can be completed within a focused scope.
When to Use This Task
Use this task when:
- The enhancement can be completed in 1-3 stories
- No significant architectural changes are required
- The enhancement follows existing project patterns
- Integration complexity is minimal
- Risk to existing system is low
Use the full brownfield PRD/Architecture process when:
- The enhancement requires multiple coordinated stories
- Architectural planning is needed
- Significant integration work is required
- Risk assessment and mitigation planning is necessary
Instructions
1. Project Analysis (Required)
Before creating the epic, gather essential information about the existing project:
Existing Project Context:
- Project purpose and current functionality understood
- Existing technology stack identified
- Current architecture patterns noted
- Integration points with existing system identified
Enhancement Scope:
- Enhancement clearly defined and scoped
- Impact on existing functionality assessed
- Required integration points identified
- Success criteria established
2. Epic Creation
Create a focused epic following this structure:
Epic Title
{{Enhancement Name}} - Brownfield Enhancement
Epic Goal
{{1-2 sentences describing what the epic will accomplish and why it adds value}}
Epic Description
Existing System Context:
- Current relevant functionality: {{brief description}}
- Technology stack: {{relevant existing technologies}}
- Integration points: {{where new work connects to existing system}}
Enhancement Details:
- What's being added/changed: {{clear description}}
- How it integrates: {{integration approach}}
- Success criteria: {{measurable outcomes}}
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.
- 5d ago First seen · 167 lines · 0 tokens per session scan A 75d79e407a35
brownfield-create-epic 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 991 tokens. A static security scan graded it A with 0 findings. It is 98% identical to brownfield-create-epic, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.