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 sourav15mukherjee/skillforge-free-skills --skill prompt-engineergit clone --depth 1 https://github.com/sourav15mukherjee/skillforge-free-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/sourav15mukherjee/skillforge-free-skills/prompt-engineer)<a href="https://agentmods.dev/skills/sourav15mukherjee/skillforge-free-skills/prompt-engineer"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/prompt-engineer/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/sourav15mukherjee/skillforge-free-skills/prompt-engineer"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/prompt-engineer.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.00054 | $0.00819 |
| Opus 5 | $0.00027 | $0.00409 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
prompt-engineer 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Engineer
Transform vague instructions into production-grade AI prompts.
Workflow
-
Understand the intent Ask the user (or infer from context):
- What is the AI supposed to do? (task)
- Who will use it? (audience)
- What model will run it? (OpenAI, Claude, Llama, etc.)
- What format should the output be? (JSON, markdown, free text)
- Any constraints? (length, tone, safety)
-
Define the role and context Write a system message that establishes:
- Who the AI is (role)
- What it knows (context/expertise)
- What it should NOT do (constraints)
- How it should respond (tone, format)
You are a senior code reviewer at a fintech company. You review pull requests for security vulnerabilities, performance issues, and maintainability. You are direct and specific — cite exact line numbers. You never approve code with SQL injection or XSS vulnerabilities. -
Create the user message template Design a structured input format:
Review this pull request: **Title:** {{pr_title}} **Description:** {{pr_description}} **Diff:**{{diff}}
Focus on: {{focus_areas}} -
Add few-shot examples Create 2-3 input/output examples that demonstrate:
- The expected quality and format
- Edge cases the model should handle
- The boundary between "in scope" and "out of scope"
-
Define output structure Specify the exact format:
{ "verdict": "approve | request_changes | comment", "summary": "One-sentence overall assessment", "findings": [ { "severity": "critical | warning | suggestion", "file": "path/to/file.ts", "line": 42, "issue": "Description of the issue", "fix": "Suggested fix" } ] } -
Add guardrails
- Token budget guidance ("keep responses under 500 tokens")
- Hallucination prevention ("only reference code in the provided diff")
- Safety boundaries ("never generate executable code in reviews")
- Fallback behavior ("if the diff is too large, summarize by file")
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.
- 12d ago First seen · 109 lines · 54 tokens per session scan A 7e60d87ac1d8
prompt-engineer is a skill published in the GitHub repository sourav15mukherjee/skillforge-free-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 819 once invoked, about $0.0003 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.
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…