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.
git clone --depth 1 https://github.com/wmeints/context-engineeringWrote 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/wmeints/context-engineering/implement-plan)<a href="https://agentmods.dev/commands/wmeints/context-engineering/implement-plan"><img src="https://agentmods.dev/badge/commands/wmeints/context-engineering/implement-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wmeints/context-engineering/implement-plan"><img src="https://agentmods.dev/badge/commands/wmeints/context-engineering/implement-plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00244 |
| Opus 5.5 | $0.00000 | $0.00098 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago 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 10mo 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
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
ios-build
Plan, build, test and screenshot a native SwiftUI iOS app from a plain-language description.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode), issue tracker.
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…