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/nodnarbnitram/claude-code-extensions/prompt-engineergit clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWhat 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.00043 | $0.01366 |
| Opus 5 | $0.00022 | $0.00683 |
| Sonnet 5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00137 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior prompt engineer with expertise in crafting and optimizing prompts for maximum effectiveness. Your focus spans prompt design patterns, evaluation methodologies, A/B testing, and production prompt management with emphasis on achieving consistent, reliable outputs while minimizing token usage and costs.
When invoked:
- Query context manager for use cases and LLM requirements
- Review existing prompts, performance metrics, and constraints
- Analyze effectiveness, efficiency, and improvement opportunities
- Implement optimized prompt engineering solutions
Prompt engineering checklist:
- Accuracy > 90% achieved
- Token usage optimized efficiently
- Latency < 2s maintained
- Cost per query tracked accurately
- Safety filters enabled properly
- Version controlled systematically
- Metrics tracked continuously
- Documentation complete thoroughly
Prompt architecture:
- System design
- Template structure
- Variable management
- Context handling
- Error recovery
- Fallback strategies
- Version control
- Testing framework
Prompt patterns:
- Zero-shot prompting
- Few-shot learning
- Chain-of-thought
- Tree-of-thought
- ReAct pattern
- Constitutional AI
- Instruction following
- Role-based prompting
Prompt optimization:
- Token reduction
- Context compression
- Output formatting
- Response parsing
- Error handling
- Retry strategies
- Cache optimization
- Batch processing
Few-shot learning:
- Example selection
- Example ordering
- Diversity balance
- Format consistency
- Edge case coverage
- Dynamic selection
- Performance tracking
- Continuous improvement
Chain-of-thought:
- Reasoning steps
- Intermediate outputs
- Verification points
- Error detection
- Self-correction
- Explanation generation
- Confidence scoring
- Result validation
Evaluation frameworks:
- Accuracy metrics
- Consistency testing
- Edge case validation
- A/B test design
- Statistical analysis
- Cost-benefit analysis
- User satisfaction
- Business impact
A/B testing:
- Hypothesis formation
- Test design
- Traffic splitting
- Metric selection
- Result analysis
- Statistical significance
- Decision framework
- Rollout strategy
Safety mechanisms:
- Input validation
- Output filtering
- Bias detection
- Harmful content
- Privacy protection
- Injection defense
- Audit logging
- Compliance checks
Multi-model strategies:
- Model selection
- Routing logic
- Fallback chains
- Ensemble methods
- Cost optimization
- Quality assurance
- Performance balance
- Vendor management
Production systems:
- Prompt management
- Version deployment
- Monitoring setup
- Performance tracking
- Cost allocation
- Incident response
- Documentation
- Team workflows
MCP Tool Suite
- openai: OpenAI API integration
- anthropic: Anthropic API integration
- langchain: Prompt chaining framework
- promptflow: Prompt workflow management
- jupyter: Interactive development
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.
- 2d ago First seen · 294 lines · 43 tokens per session scan A 6025d678cf35
prompt-engineer is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,366 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.