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/wmeints/context-engineering/implement-plangit clone --depth 1 https://github.com/wmeints/context-engineeringWhat 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.00244 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
implement-plan 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.
What it actually says
Implement requirements
Implement a feature based on the requirements document.
Requirements file: $ARGUMENTS
Execution process
- Load the requirements document
- Read the specified requirements document
- Understand the context and requirements
- Follow all instructions in the requirements document
- Ensure you have all needed context to implement the requirements fully
- Do more web and code base search as necessary
- Plan the implementation
- Think before you execute the plan. Create a comprehensive plan addressing all requirements.
- Break down complex tasks into smaller, manageable steps using your TODO tools.
- Use the TodoWrite tool to create and track your implementation plan.
- Identity implementation patterns from existing code to follow.
- Execute the plan
- Implement the requirements from the requirements document
- Write the code necessary.
- Validate
- Run each validation gate
- Fix any failures
- Re-run until all validation gates pass
- Complete
- Ensure all checklist items are done
- Run final validation suite
- Report completion status
- Read the requirements document again to ensure you've implemented everything
- Reference the requirements document
- You can always reference the requirements document again.
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 · 45 lines · 0 tokens per session scan A 233eddc225e0
implement-plan is a command published in the GitHub repository wmeints/context-engineering (37 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 244 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
al-agent-instructions-create
Generate optimized natural language instructions for Business Central agents (Designer or SDK). Follows Responsibilities-Guidelines-Instructions framework. Use when writing agent instructions or creating InstructionsV1.txt.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
ruanzhu
Command "ruanzhu" from doccker/cc-use-exp, covering /ruanzhu - 软著源代码docx生成, 参数映射, 禁止事项, 唯一允许的操作 and 说明.
choose-model
Compare current models across configured AI providers and produce an executable plan without running paid work. Use when the user asks which model or provider should perform a task.
setup
Check whether GitHub Copilot CLI is installed, authenticated, and ready for delegation.
review
Review code across five axes with categorized findings.