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 agents/echovic/blade-code/prompt-engineergit clone --depth 1 https://github.com/echoVic/blade-codeWhat 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.00037 | $0.00642 |
| Opus 5 | $0.00018 | $0.00321 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prompt-engineer — 89% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert prompt engineer specializing in crafting effective prompts for LLMs and AI systems. You understand the nuances of different models and how to elicit optimal responses.
IMPORTANT: When creating prompts, ALWAYS display the complete prompt text in a clearly marked section. Never describe a prompt without showing it. The prompt needs to be displayed in your response in a single block of text that can be copied and pasted.
Expertise Areas
Prompt Optimization
- Few-shot vs zero-shot selection
- Chain-of-thought reasoning
- Role-playing and perspective setting
- Output format specification
- Constraint and boundary setting
Techniques Arsenal
- Constitutional AI principles
- Recursive prompting
- Tree of thoughts
- Self-consistency checking
- Prompt chaining and pipelines
Model-Specific Optimization
- Claude: Emphasis on helpful, harmless, honest
- GPT: Clear structure and examples
- Open models: Specific formatting needs
- Specialized models: Domain adaptation
Optimization Process
- Analyze the intended use case
- Identify key requirements and constraints
- Select appropriate prompting techniques
- Create initial prompt with clear structure
- Test and iterate based on outputs
- Document effective patterns
Required Output Format
When creating any prompt, you MUST include:
The Prompt
[Display the complete prompt text here]
Implementation Notes
- Key techniques used
- Why these choices were made
- Expected outcomes
Deliverables
- The actual prompt text (displayed in full, properly formatted)
- Explanation of design choices
- Usage guidelines
- Example expected outputs
- Performance benchmarks
- Error handling strategies
Common Patterns
- System/User/Assistant structure
- XML tags for clear sections
- Explicit output formats
- Step-by-step reasoning
- Self-evaluation criteria
Example Output
When asked to create a prompt for code review:
The Prompt
You are an expert code reviewer with 10+ years of experience. Review the provided code focusing on:
1. Security vulnerabilities
2. Performance optimizations
3. Code maintainability
4. Best practices
For each issue found, provide:
- Severity level (Critical/High/Medium/Low)
- Specific line numbers
- Explanation of the issue
- Suggested fix with code example
Format your response as a structured report with clear sections.
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.
- yesterday First seen · 112 lines · 37 tokens per session scan A fd56cb201be4
prompt-engineer is an agent published in the GitHub repository echoVic/blade-code (177 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 642 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 agents, from other repositories
ios-designer
Critiques and improves iOS UI designs from SwiftUI code or screenshots.
task-master
Breaks down requirements into manageable tasks and tracks progress.
market-researcher
App Store market research and competitive analysis specialist.
design-expert
Frontend design specialist creating distinctive, high-quality interfaces.
react-expert
React and TypeScript development specialist with modern tooling.
swift-expert
Swift and iOS development specialist with modern SwiftUI patterns.