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/generate-ai-frontend-prompt)<a href="https://agentmods.dev/commands/cakemail/cakemail-api-documentation-mcp/generate-ai-frontend-prompt"><img src="https://agentmods.dev/badge/commands/cakemail/cakemail-api-documentation-mcp/generate-ai-frontend-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/cakemail/cakemail-api-documentation-mcp/generate-ai-frontend-prompt"><img src="https://agentmods.dev/badge/commands/cakemail/cakemail-api-documentation-mcp/generate-ai-frontend-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.00000 | $0.01021 |
| Opus 5 | $0.00000 | $0.00511 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
generate-ai-frontend-prompt 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 9d 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
94% identical to generate-ai-frontend-prompt — 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/generate-ai-frontend-prompt Task
When this command is used, execute the following task:
Create AI Frontend Prompt Task
Purpose
To generate a masterful, comprehensive, and optimized prompt that can be used with any AI-driven frontend development tool (e.g., Vercel v0, Lovable.ai, or similar) to scaffold or generate significant portions of a frontend application.
Inputs
- Completed UI/UX Specification (
front-end-spec.md) - Completed Frontend Architecture Document (
front-end-architecture) or a full stack combined architecture such asarchitecture.md - Main System Architecture Document (
architecture- for API contracts and tech stack to give further context)
Key Activities & Instructions
1. Core Prompting Principles
Before generating the prompt, you must understand these core principles for interacting with a generative AI for code.
- Be Explicit and Detailed: The AI cannot read your mind. Provide as much detail and context as possible. Vague requests lead to generic or incorrect outputs.
- Iterate, Don't Expect Perfection: Generating an entire complex application in one go is rare. The most effective method is to prompt for one component or one section at a time, then build upon the results.
- Provide Context First: Always start by providing the AI with the necessary context, such as the tech stack, existing code snippets, and overall project goals.
- Mobile-First Approach: Frame all UI generation requests with a mobile-first design mindset. Describe the mobile layout first, then provide separate instructions for how it should adapt for tablet and desktop.
2. The Structured Prompting Framework
To ensure the highest quality output, you MUST structure every prompt using the following four-part framework.
- High-Level Goal: Start with a clear, concise summary of the overall objective. This orients the AI on the primary task.
- Example: "Create a responsive user registration form with client-side validation and API integration."
- Detailed, Step-by-Step Instructions: Provide a granular, numbered list of actions the AI should take. Break down complex tasks into smaller, sequential steps. This is the most critical part of the prompt.
- Example: "1. Create a new file named
RegistrationForm.js. 2. Use React hooks for state management. 3. Add styled input fields for 'Name', 'Email', and 'Password'. 4. For the email field, ensure it is a valid email format. 5. On submission, call the API endpoint defined below."
- Example: "1. Create a new file named
- Code Examples, Data Structures & Constraints: Include any relevant snippets of existing code, data structures, or API contracts. This gives the AI concrete examples to work with. Crucially, you must also state what not to do.
- Example: "Use this API endpoint:
POST /api/register. The expected JSON payload is{ "name": "string", "email": "string", "password": "string" }. Do NOT include a 'confirm password' field. Use Tailwind CSS for all styling."
- Example: "Use this API endpoint:
- Define a Strict Scope: Explicitly define the boundaries of the task. Tell the AI which files it can modify and, more importantly, which files to leave untouched to prevent unintended changes across the codebase.
- Example: "You should only create the
RegistrationForm.jscomponent and add it to thepages/register.jsfile. Do NOT alter theNavbar.jscomponent or any other existing page or component."
- Example: "You should only create the
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.
- 9d ago First seen · 58 lines · 0 tokens per session scan A 2b3347782d8e
generate-ai-frontend-prompt 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 1,021 tokens. A static security scan graded it A with 0 findings. It is 94% identical to generate-ai-frontend-prompt, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
openui-prompt
Generate or regenerate the system prompt from the component library.
stripe-backend
Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.
python-command
Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.
add-ai-feature
Guide the user through adding AI capabilities to their Cloudflare Workers + React application.
generate-ai-frontend-prompt
When this command is used, execute the following task.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.