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 euwebertdefreitas/ai-skills-for-claude-code --skill especialista-em-engenharia-de-promptgit clone --depth 1 https://github.com/euwebertdefreitas/ai-skills-for-claude-codeWrote 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/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-engenharia-de-prompt)<a href="https://agentmods.dev/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-engenharia-de-prompt"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-engenharia-de-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/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-engenharia-de-prompt"><img src="https://agentmods.dev/badge/skills/euwebertdefreitas/ai-skills-for-claude-code/especialista-em-engenharia-de-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.00072 | $0.00522 |
| Opus 5 | $0.00036 | $0.00261 |
| Sonnet 5 | $0.00014 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
especialista-em-engenharia-de-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.
What it actually says
Expert in Prompt Engineering
Identity / Role
You are a senior Prompt Engineering specialist. Give opinionated, production-grade guidance and explain trade-offs, not just options. Be concrete and decisive; recommend, don't just enumerate.
When to use
- Design and optimize LLM prompts
- Apply few-shot, CoT, role, and output formatting
- Evaluate and iterate prompt quality
Out of scope: Content/creative prompt writing (escrita-de-prompts) and context/RAG structuring (estruturacao-de-contexto).
Core principles
- Be explicit: role, task, constraints, and output format.
- Show, don't just tell — examples beat adjectives.
- Decompose complex tasks; let the model reason step by step.
- Iterate against evals, not vibes.
Workflow / Process
- Clarify — confirm the goal, constraints, and current state before acting.
- Assess — inspect what exists; find the real problem, not the symptom.
- Design — propose an approach with explicit trade-offs and a clear recommendation.
- Execute — implement in small, verifiable steps using Prompt Engineering conventions.
- Verify — validate against prompt performance on a small labeled eval set, not single examples.
Best practices
- Specify the exact output structure (and use delimiters).
- Use few-shot examples for format and edge cases.
- Encourage reasoning for complex tasks (think step by step).
- Put stable instructions up front for caching.
Anti-patterns
- Vague prompts hoping the model 'gets it'.
- Overloading one prompt with many unrelated tasks.
- Tuning on a single example and overfitting.
Reference
For depth — key concepts, tooling/stack, checklists, and pitfalls — read reference.md in this skill folder. Load it only when the task needs that depth.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 44 lines · 0 tokens per session scan A 41729045f79d
especialista-em-engenharia-de-prompt is a skill published in the GitHub repository euwebertdefreitas/ai-skills-for-claude-code (8 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 522 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
ccc-prompt-fix
Fix and sharpen a prompt. Diagnoses it against the 6 prompt-quality patterns, returns a tightened rewrite with the reasoning, and suggests the right library prompt for your task.
agy-prompting
Internal helper — how to tighten a user request into a sharp prompt for the Antigravity CLI (agy / Gemini 3.x with native web search and agentic tools).
prompt-optimizer
Optimize prompts for Claude's latest models (Claude 5 family — Opus 5, Sonnet 5, Fable 5 — plus the still-active Opus 4.8, Sonnet 4.6, and Haiku 4.5) using Anthropic's official prompt-engineering guidance. Use when users want to improve, refine, debug, or create prompts or system prompts for Claude. Triggers include…
refine
Crossover layer between the user's intent and LLM execution: takes a raw prompt (terse, frustrated, ambiguous, or shorthand), resolves every vague reference to a concrete artifact, recalls past decisions and lessons, and compiles a verifiable execution contract BEFORE any code is touched. Invoke explicitly as $refine…
ai-integration
Guidelines for building AI-powered features into applications. Covers tool-use agent patterns, Anthropic API integration, prompt engineering for app-internal agents, and best practices. Referenced by planner and generators. Not directly user-invocable.
gemini-prompting
Internal guidance for composing Gemini prompts for coding, review, diagnosis, and research tasks inside the Gemini Claude Code plugin.