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 skills add u2n4/ai-dev-skills --skill prompt-generatorgit clone --depth 1 https://github.com/u2n4/ai-dev-skillsWrote 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/skills/u2n4/ai-dev-skills/prompt-generator)<a href="https://agentmods.dev/skills/u2n4/ai-dev-skills/prompt-generator"><img src="https://agentmods.dev/badge/skills/u2n4/ai-dev-skills/prompt-generator/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/skills/u2n4/ai-dev-skills/prompt-generator"><img src="https://agentmods.dev/badge/skills/u2n4/ai-dev-skills/prompt-generator.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.00056 | $0.01726 |
| Opus 5 | $0.00028 | $0.00863 |
| Sonnet 5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
prompt-generator 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.
How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Prompt Generator
When to Use This Skill
Activate when the user asks to:
- Create a prompt for Claude Code
- Set up an Agent Team for a project
- Design a multi-phase workflow
- Generate a professional Claude Code instruction set
- Build a CLAUDE.md for a project
- Create task-specific prompts with proper structure
Prompt Architecture
The 5-Layer Prompt Structure
Every professional Claude Code prompt should include these layers:
Layer 1: Context & Role
Define WHO Claude is and WHAT the project context is.
You are an expert [role] with deep knowledge of [domains].
<context>
[Project description, current state, relevant background]
</context>
Layer 2: Task Definition
Define WHAT needs to be done with clear phases.
<task>
## Phase 1: [Research/Audit]
[Steps with specific actions]
## Phase 2: [Implementation]
[Steps with expected outputs]
## Phase 3: [Verification]
[Testing and validation steps]
</task>
Layer 3: Requirements & Constraints
Define HOW the work should be done.
<requirements>
- [Quality standards]
- [Technical constraints]
- [Output format]
</requirements>
<constraints>
- NEVER [dangerous action]
- ALWAYS [safety requirement]
- [Boundary conditions]
</constraints>
Layer 4: Agent Team Pattern
For complex tasks, define specialized agent roles.
## Agent Team
### Research Agent
- Role: Gather information and audit current state
- Tools: WebSearch, Grep, Glob, Read
- Output: Research report
### Implementation Agent
- Role: Execute the plan
- Tools: Write, Edit, Bash
- Output: Working code
### Review Agent
- Role: Verify quality and security
- Tools: Read, Grep, Bash
- Output: Review report with issues
Layer 5: Output Controls
Define verification checkpoints and stop conditions.
## Verification Checkpoint
Present to me:
1. [Deliverable 1]
2. [Deliverable 2]
3. [Status summary]
**STOP HERE. Wait for my confirmation before proceeding.**
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 · 323 lines · 56 tokens per session scan A 6eaa21691a85
prompt-generator is a skill published in the GitHub repository u2n4/ai-dev-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 1,726 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
seedance-vocab-en
This skill should be used when an English Seedance 2.0 prompt needs clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints. Route blocked prompts through seedance-filter for context and boundary review.
ideogram4
Prompting patterns for Ideogram 4 text-to-image — best-in-class in-image text rendering and exact color/layout control via structured JSON captions. Use when generating images that need legible on-image text (title cards, thumbnails, logos, signage, CTAs), precise brand colors, or controlled spatial layout. Triggers…