prompt-engineering

A guide for improving instructions given to AI models such as Claude, OpenAI, and Gemini. It examines a draft prompt, chooses techniques for the task and model, and provides revised examples and checks.

In plain words
What is it for?
Use it to diagnose, rewrite, and evaluate prompts for different AI models. It includes worked examples, a quality checklist, and evaluation guidance.
Why use it?
Unclear or poorly structured prompts can produce inconsistent results. The guide helps identify weaknesses and turn an instruction into a clearer, more repeatable request.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add PhAlves23/prompt-engineering-skill
agentmods
npx agentmods add plugins/phalves23/prompt-engineering-skill/prompt-engineering
Clone the repo
git clone --depth 1 https://github.com/PhAlves23/prompt-engineering-skill

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

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 2d 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.

plugins/prompt-engineering/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "prompt-engineering",
  "displayName": "Prompt Engineering",
  "description": "Optimizes and rewrites prompts using proven prompt engineering techniques: draft diagnosis, canonical structure, technique selection by task type and target model (Claude 4.x, OpenAI, Gemini), with worked examples, a quality checklist, and an evaluation guide.",
  "version": "1.1.0",
  "author": {
    "name": "Paulo Henrique Andrade Alves"
  },
  "homepage": "https://github.com/PhAlves23/prompt-engineering-skill",
  "repository": "https://github.com/PhAlves23/prompt-engineering-skill",
  "license": "MIT",
  "keywords": [
    "prompt-engineering",
    "prompts",
    "claude",
    "llm",
    "skill"
  ]
}
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. 2d ago First seen · 20 lines scan A 872d13cec025

Subscribe to this mod's changes

prompt-engineering is a plugin published in the GitHub repository PhAlves23/prompt-engineering-skill (9 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.