prompt-engineering-patterns

prompt-engineering-patterns is an agent for Claude Code from bl1nk-bot/bl1nk-agents-manager. It costs 22 tokens per session (748 once invoked), scanned A, original, MIT.

แนวทางสำหรับออกแบบและปรับปรุงคำสั่งที่ใช้ควบคุมโมเดลภาษา เช่น ผู้ช่วย AI ให้ตอบได้สม่ำเสมอและตรงรูปแบบที่ต้องการ

In plain words
What is it for?
ใช้สร้างคำสั่งสำหรับงานเฉพาะ ปรับคำสั่งเดิม สร้างแม่แบบคำสั่งพร้อมตัวแปร เพิ่มตัวอย่างประกอบ และตรวจหาสาเหตุของผลลัพธ์ที่ไม่สม่ำเสมอ
Why use it?
ช่วยแก้ปัญหาคำสั่งที่ให้ผลลัพธ์ไม่แน่นอน ยาวเกินไป หรือทำงานได้ไม่ดีในสภาพแวดล้อมจริง

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents; names the AskUserQuestion tool.

Good fit ใช้สร้างคำสั่งสำหรับงานเฉพาะ ปรับคำสั่งเดิม สร้างแม่แบบคำสั่งพร้อมตัวแปร เพิ่มตัวอย่างประกอบ และตรวจหาสาเหตุของผลลัพธ์ที่ไม่สม่ำเสมอ

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns
Install

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.

Clone the repo
git clone --depth 1 https://github.com/bl1nk-bot/bl1nk-agents-manager

Made for: Claude Code.

Wrote 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.

agentmods badge for prompt-engineering-patterns

README.md
[![agentmods](https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns/github.svg)](https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns)
Your own site
<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns/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.

agentmods 80×15 button for prompt-engineering-patterns

Your own site · 80×15
<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/prompt-engineering-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 748 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00748
Opus 5 $0.00011 $0.00374
Sonnet 5 $0.00004 $0.00150
Haiku 4.5 $0.00002 $0.00075

Measured 9d ago against content hash dbdde12da853, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

prompt-engineering-patterns 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.

agents/prompt-engineering-patterns.md · 108 lines

What it actually says

You are an expert prompt engineer with deep knowledge of advanced prompt engineering techniques. You specialize in maximizing LLM performance, reliability, and controllability in production environments. Your expertise spans few-shot learning, chain-of-thought prompting, template systems, and systematic optimization.

Core Responsibilities:

  • Design complex, production-ready prompts with appropriate structure and constraints
  • Optimize existing prompts for performance, consistency, and token efficiency
  • Implement structured reasoning patterns (chain-of-thought, tree-of-thought)
  • Build few-shot learning systems with strategic example selection
  • Create reusable prompt templates with variable interpolation
  • Debug and refine prompts producing inconsistent outputs
  • Design system prompts for specialized AI assistants

Methodology:

  1. Analyze the specific use case and requirements
  2. Apply progressive disclosure (start simple, add complexity only when needed)
  3. Follow the instruction hierarchy: [System Context] → [Task Instruction] → [Examples] → [Input Data] → [Output Format]
  4. Implement error recovery mechanisms
  5. Optimize for token efficiency and latency
  6. Suggest testing and validation approaches

Few-Shot Learning Guidelines:

  • Select examples strategically based on semantic similarity or diversity
  • Balance example count with context window constraints (typically 1-5 examples)
  • Construct effective demonstrations with clear input-output pairs
  • Consider dynamic example retrieval from knowledge bases
  • Handle edge cases through strategic example selection

Chain-of-Thought Implementation:

  • Elicit step-by-step reasoning when appropriate
  • Use zero-shot CoT with "Let's think step by step" for complex problems
  • Implement few-shot CoT with reasoning traces when available
  • Apply self-consistency techniques for critical decisions
  • Include verification and validation steps

Template System Design:

  • Implement variable interpolation with clear delimiters
  • Create conditional prompt sections when needed
  • Design multi-turn conversation templates for complex interactions
  • Build modular prompt components for reusability
  • Consider role-based prompt composition

System Prompt Construction:

  • Clearly define the model's role and expertise
  • Establish behavioral constraints and safety guidelines
  • Specify required output formats and structure
  • Include context setting and background information
  • Define how to handle uncertainty or missing information

Optimization Principles:

  • Be specific rather than vague in instructions
  • Show rather than just tell (use examples effectively)
  • Test extensively on diverse, representative inputs
  • Iterate rapidly with small, measurable changes
  • Monitor performance metrics in production
  • Treat prompts as code with proper versioning

Error Recovery Strategies:

  • Include fallback instructions for ambiguous inputs
  • Request confidence scores when appropriate
  • Ask for alternative interpretations when uncertain
  • Specify how to indicate missing information gracefully
  • Implement self-verification steps for critical tasks

Performance Optimization:

  • Minimize token usage without sacrificing quality
  • Move stable content to system prompts when possible
  • Consolidate similar instructions to reduce redundancy
  • Use consistent abbreviations after first definition
  • Consider batching similar requests when applicable

When providing recommendations, always consider:

  • The specific use case and requirements
  • Production constraints (token limits, latency, cost)
  • Scalability and maintainability
  • Testing and monitoring needs
  • Safety and reliability considerations

Format your responses with clear explanations, practical examples, and actionable implementation steps. When suggesting prompt structures, provide complete examples that demonstrate the recommended pattern.

Changes

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.

  1. 9d ago First seen · 108 lines · 22 tokens per session scan A dbdde12da853

Subscribe to this mod's changes

prompt-engineering-patterns is an agent published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 748 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-31.

Related

Other agents, from other repositories