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 Owl-Listener/ai-design-skills --skill template-designgit clone --depth 1 https://github.com/Owl-Listener/ai-design-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/owl-listener/ai-design-skills/template-design)<a href="https://agentmods.dev/skills/owl-listener/ai-design-skills/template-design"><img src="https://agentmods.dev/badge/skills/owl-listener/ai-design-skills/template-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/skills/owl-listener/ai-design-skills/template-design"><img src="https://agentmods.dev/badge/skills/owl-listener/ai-design-skills/template-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.00014 | $0.00522 |
| Opus 5 | $0.00007 | $0.00261 |
| Sonnet 5 | $0.00003 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
template-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 12d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Design
A prompt template is a reusable prompt structure with variable slots that get filled at runtime. Templates create consistency across similar tasks and make prompt management scalable.
Template Anatomy
A template has:
- Fixed text: The parts that stay the same every time (instructions, format, role)
- Variables: Slots that get filled with specific content (user input, retrieved data, configuration)
- Conditional sections: Parts that appear or disappear based on context
- Default values: What fills a variable if no specific value is provided
Designing Variables
Each variable should be:
- Named clearly:
{user_query}not{input1} - Typed: Is it free text, a selection from options, a number, a boolean?
- Bounded: What are valid values? What's the maximum length?
- Documented: What is this variable for? Where does its value come from?
- Defaulted: What happens if the value is missing?
Template Patterns
- Task template: A template for a specific type of task. Variables capture the task-specific details while instructions remain constant.
- Persona template: A template where the persona is variable but the task structure is fixed. Useful for multi-persona products.
- Format template: A template where the output format is variable but the analysis approach is fixed.
- Escalation template: A base template with additional sections that activate at higher complexity levels.
Template Composition
Complex prompts can be built from smaller templates:
- Base template: Core instructions that apply to everything
- Task overlay: Task-specific instructions layered on top
- Context injection: Retrieved information inserted at a specific point
- User preferences: Personal settings that modify behavior
Template Quality Criteria
- Consistency: The template produces reliably similar outputs for similar inputs
- Flexibility: The variables allow enough variation for diverse use cases
- Clarity: The template is easy to read, maintain, and modify
- Testability: You can verify the template works with a standard set of test inputs
- Maintainability: Changes to one part don't break other parts
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.
- 12d ago First seen · 43 lines · 14 tokens per session scan A 59d4f28e2551
template-design is a skill published in the GitHub repository Owl-Listener/ai-design-skills (173 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 522 once invoked, about $0.0001 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-30.
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…