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 hajekim/agentic-design-patterns-extension --skill appendix-prompt-engineeringgit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-extensionWrote 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/hajekim/agentic-design-patterns-extension/appendix-prompt-engineering)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-extension/appendix-prompt-engineering"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-extension/appendix-prompt-engineering.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.00421 | $0.03401 |
| Opus 5 | $0.00211 | $0.01700 |
| Sonnet 5 | $0.00084 | $0.00680 |
| Haiku 4.5 | $0.00042 | $0.00340 |
Grade A, and why
appendix-prompt-engineering 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 7d 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 appendix-prompt-engineering — 3 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Appendix A - Prompt Engineering
Overview
Prompt Engineering is the disciplined practice of crafting, iterating, and optimizing the inputs given to language models to produce reliable, high-quality outputs. It is not a simple act of asking questions — it is a structured engineering discipline that transforms a general-purpose language model into a specialized, highly capable tool for specific tasks.
For agents, prompting is the foundational layer: every agentic pattern depends on well-crafted prompts. A powerful model with a poor prompt produces poor results. A well-engineered prompt transforms model outputs from probabilistic guesses into deterministic, structured, trustworthy cognitive operations.
Core Principle: Treat prompts as code — version them, test them, iterate them, and document what works and why.
When This Skill Applies
Activate this pattern when:
- Building any LLM-powered agent that needs reliable, structured outputs
- Writing system prompts, user instructions, or tool descriptions for agents
- An agent produces inconsistent, hallucinated, or poorly formatted responses
- You need structured data (JSON, XML) from model outputs
- Implementing Chain-of-Thought, ReAct, or few-shot reasoning patterns
- Testing and comparing different prompt strategies
- Preparing prompts for production deployment
Rule of thumb: Every agent interaction is a prompt. Engineer them deliberately — don't leave agent behavior to chance.
Prompting Technique Hierarchy
Zero-Shot: No examples — just instructions
→ Simple tasks with clear instructions
One-Shot: One example — demonstrate the pattern
→ When output format matters
Few-Shot: 2–5 examples — show the range
→ Complex tasks, classification, structured extraction
Chain-of-Thought: "Think step by step" + examples
→ Reasoning tasks, math, multi-step problems
ReAct: Thought → Action → Observation loop
→ Agents using tools in an iterative loop
DEFINE → PLAN → ACTION Workflow
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.
- 7d ago First seen · 349 lines · 421 tokens per session scan A 650e6585185e
appendix-prompt-engineering is a skill published in the GitHub repository hajekim/agentic-design-patterns-extension (1 stars, last pushed 5mo ago), licensed MIT. It adds 421 tokens to every session and 3,401 once invoked, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to appendix-prompt-engineering, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
prompt engineering
Use this skill when asked to create, refine, analyze, or optimize prompts for Large Language Models (LLMs). This skill ensures adherence to prompt engineering best practices and enforces a rigorous design workflow.
prompt-optimizer
Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite…
gemini-api
Google Gemini API patterns for Python and TypeScript. Covers content generation, streaming, tool use (function calling), vision, system instructions, context caching, batch requests, and agent workflows. Use when building applications with the Gemini API or Google Generative AI SDKs.
appendix-prompt-engineering
This skill should be used when the user wants to learn "prompt engineering", "few-shot prompting", "zero-shot prompting", "chain of thought prompting", "structured output prompting", "role prompting", "system prompt design", "prompt best practices", "CoT prompting", "Pydantic structured output", "prompt iteration"…
prompt-chaining
This skill should be used when the user wants to "chain prompts", "build a pipeline", "break down complex tasks into steps", "sequential LLM calls", "multi-step reasoning", "pipeline pattern", "sequential agent pipeline", "multi-step prompt pipeline", "LLM chain", "step-by-step agent", "prompt pipeline", "decompose…
reasoning
This skill should be used when the user wants to "chain-of-thought prompting", "ReAct agent", "tree of thought", "step-by-step reasoning", "structured reasoning agents", "agent thinking", "scratchpad reasoning", "self-consistency", "reasoning traces", "deliberate thinking", "agent metacognition", "think before…