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/test-design)<a href="https://agentmods.dev/commands/cakemail/cakemail-api-documentation-mcp/test-design"><img src="https://agentmods.dev/badge/commands/cakemail/cakemail-api-documentation-mcp/test-design/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/cakemail/cakemail-api-documentation-mcp/test-design"><img src="https://agentmods.dev/badge/commands/cakemail/cakemail-api-documentation-mcp/test-design.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.00000 | $0.01180 |
| Opus 5.5 | $0.00000 | $0.00472 |
| Sonnet 5.5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
test-design 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 1mo 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
100% identical to test-design — 0 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test-design Task
When this command is used, execute the following task:
test-design
Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
Inputs
required:
- story_id: '{epic}.{story}' # e.g., "1.3"
- story_path: '{devStoryLocation}/{epic}.{story}.*.md' # Path from core-config.yaml
- story_title: '{title}' # If missing, derive from story file H1
- story_slug: '{slug}' # If missing, derive from title (lowercase, hyphenated)
Purpose
Design a complete test strategy that identifies what to test, at which level (unit/integration/e2e), and why. This ensures efficient test coverage without redundancy while maintaining appropriate test boundaries.
Dependencies
data:
- test-levels-framework.md # Unit/Integration/E2E decision criteria
- test-priorities-matrix.md # P0/P1/P2/P3 classification system
Process
1. Analyze Story Requirements
Break down each acceptance criterion into testable scenarios. For each AC:
- Identify the core functionality to test
- Determine data variations needed
- Consider error conditions
- Note edge cases
2. Apply Test Level Framework
Reference: Load test-levels-framework.md for detailed criteria
Quick rules:
- Unit: Pure logic, algorithms, calculations
- Integration: Component interactions, DB operations
- E2E: Critical user journeys, compliance
3. Assign Priorities
Reference: Load test-priorities-matrix.md for classification
Quick priority assignment:
- P0: Revenue-critical, security, compliance
- P1: Core user journeys, frequently used
- P2: Secondary features, admin functions
- P3: Nice-to-have, rarely used
4. Design Test Scenarios
For each identified test need, create:
test_scenario:
id: '{epic}.{story}-{LEVEL}-{SEQ}'
requirement: 'AC reference'
priority: P0|P1|P2|P3
level: unit|integration|e2e
description: 'What is being tested'
justification: 'Why this level was chosen'
mitigates_risks: ['RISK-001'] # If risk profile exists
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.
- 1mo ago First seen · 181 lines · 0 tokens per session scan A 15c1261b0e55
test-design is a command published in the GitHub repository cakemail/cakemail-api-documentation-mcp (0 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,180 tokens. A static security scan graded it A with 0 findings. It is 100% identical to test-design, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
test
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.