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 agentmods add skills/bdiasti/maestro-bundle-cli/prompt-engineeringnpx skills add bdiasti/maestro-bundle-cli --skill prompt-engineeringgit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWrote 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/bdiasti/maestro-bundle-cli/prompt-engineering)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/prompt-engineering"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/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 | $0.00032 | $0.01333 |
| Opus 5 | $0.00016 | $0.00666 |
| Sonnet 5 | $0.00006 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
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 4d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Engineering
Craft effective system prompts for AI agents using structured templates, best practices, and iterative refinement.
When to Use
- Writing a new system prompt for an agent
- Improving an underperforming agent's instructions
- Creating role-specific prompts for multi-agent systems
- Reviewing prompts for anti-patterns and clarity issues
- Optimizing prompts to reduce token usage without losing quality
Available Operations
- Write a structured system prompt from scratch
- Audit an existing prompt for anti-patterns
- Refine a prompt based on agent evaluation results
- Create few-shot examples for a prompt
- Optimize prompt token count
Multi-Step Workflow
Step 1: Define the Prompt Structure
Every agent system prompt should follow this 6-part structure:
1. IDENTITY -- Who the agent is
2. OBJECTIVE -- What it must achieve
3. TOOLS -- What it has available
4. RULES -- Non-negotiable constraints
5. FORMAT -- How to structure output
6. EXAMPLES -- Concrete demonstrations
Step 2: Write the System Prompt
Use the template below, filling in each section with specific details.
SYSTEM_PROMPT = """
## Identity
You are {role}, specialized in {specialty}.
## Objective
Your mission is {primary_objective}. You work within Maestro,
a development governance platform.
## Available Tools
{list_of_tools_with_descriptions}
## Rules
1. Always follow the {bundle_name} bundle for code standards
2. Every commit must reference the task: {task_id}
3. Work only in the designated worktree: {worktree_path}
4. Report progress at every significant step
5. Request human review for destructive operations
## Response Format
- For code: use fenced code blocks with language specified
- For decisions: justify with "why"
- For errors: include context and suggested fix
## Example
Task: "Create endpoint GET /api/v1/demands"
Action: Create controller, use case, repository following Clean Architecture
Branch: feature/backend-{task_id}
"""
What ships with it
2 files 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.
- 4d ago First seen · 159 lines · 32 tokens per session scan A 0a283aec6bf1
prompt-engineering is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 1,333 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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-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…
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…
prompt-master
Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other…
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…
seedance-antislop
This skill should be used when a Seedance 2.0 prompt contains generic AI filler, hollow superlatives, vague cinematic language, bloated adjectives, weak verbs, or needs sharper production-specific wording.