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 commands/coleam00/context-engineering-intro/execute-template-prpgit clone --depth 1 https://github.com/coleam00/context-engineering-introWrote 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/commands/coleam00/context-engineering-intro/execute-template-prp)<a href="https://agentmods.dev/commands/coleam00/context-engineering-intro/execute-template-prp"><img src="https://agentmods.dev/badge/commands/coleam00/context-engineering-intro/execute-template-prp.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.00000 | $0.01476 |
| Opus 5 | $0.00000 | $0.00738 |
| Sonnet 5 | $0.00000 | $0.00295 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
execute-template-prp 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Template Generation PRP
Execute a comprehensive template generation PRP to create a complete context engineering template package for a specific technology/framework.
PRP File: $ARGUMENTS
Execution Process
-
Load Template Generation PRP
- Read the specified template generation PRP file completely
- Understand the target technology and all requirements
- Review all web research findings documented in the PRP
- Follow all instructions for template package creation
-
ULTRATHINK - Template Package Design
- Create comprehensive implementation plan
- Plan the complete template package structure based on PRP research
- Design domain-specific context engineering adaptations
- Map technology patterns to context engineering principles
- Plan all required files and their relationships
-
Generate Complete Template Package
- Create complete directory structure for the technology use case
- Generate domain-specific CLAUDE.md with global rules
- Create specialized template PRP generation and execution commands
- Develop domain-specific base PRP template with research findings
- Include comprehensive examples and documentation from web research
-
Validate Template Package
- Run all validation commands specified in the PRP
- Verify all required files are created and properly formatted
- Test template structure completeness and accuracy
- Check integration with base context engineering framework
-
Quality Assurance
- Ensure template follows all context engineering principles
- Verify domain-specific patterns are accurately represented
- Check validation loops are appropriate and executable for the technology
- Confirm template is immediately usable for the target technology
-
Complete Implementation
- Review template package against all PRP requirements
- Ensure all success criteria from the PRP are met
- Validate template is production-ready
Template Package Requirements
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 · 165 lines · 0 tokens per session scan A aa07f1de1dc1
execute-template-prp is a command published in the GitHub repository coleam00/context-engineering-intro (13,822 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,476 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.