Borrowing it
Nothing to install: this file belongs to webhook-co/webhook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/webhook-co/webhook/main/.claude/commands/execute-plan.mdgit clone --depth 1 https://github.com/webhook-co/webhookWrote 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/webhook-co/webhook/execute-plan)<a href="https://agentmods.dev/commands/webhook-co/webhook/execute-plan"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/execute-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/webhook-co/webhook/execute-plan"><img src="https://agentmods.dev/badge/commands/webhook-co/webhook/execute-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.00439 |
| Opus 5.5 | $0.00000 | $0.00176 |
| Sonnet 5.5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
execute-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
/execute-plan
Implement an agreed plan in reviewed batches, not one giant uninterrupted run. Use this after a plan
exists (from /brainstorming, /feature-dev, or a written design).
How to run
- Confirm the plan. Restate the batches you'll implement and their order. If there's no clear
plan yet, stop and ask for one (or run
/brainstormingfirst). Don't improvise scope. - Work one batch at a time. For each batch:
- Implement it under TDD — failing test first, then the minimum code to pass, then refactor (see
the
test-driven-developmentskill). - Keep changes scoped to the batch; don't drift into unrelated edits.
- Implement it under TDD — failing test first, then the minimum code to pass, then refactor (see
the
- Review checkpoint after each batch. Hand the diff to the
code-revieweragent (and theqa-test-revieweragent when behavior on a correctness-critical path changed — signing/verification, dedup, retries, ordering, replay, metering). Address must-fix findings before moving on. - Pause for me at each checkpoint with a one-line status: what landed, what the review said, and what's next. Don't barrel through all batches silently.
- Summarize at the end: what changed, test status, follow-ups, and anything needing human verification.
Hard rules
- Never bypass the gate. No
git commit --no-verify/git push --no-verify, no.only/.skip/ disabled tests, no lowered coverage thresholds. If the pre-commit/lint-staged hook fails, fix the root cause and make a new commit — CI required checks are the real gate and have no bypass. - Human-UI-testing hard stop. If a batch needs human visual/interaction/copy verification, stop and flag it for human testing; don't mark it done on your own.
- Keep CLI/API/web/MCP at parity; reuse
shared/types. Stay public-safe (no pricing/account IDs).
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 · 29 lines · 0 tokens per session scan A db5ec31d9ff5
execute-plan is a command published in the GitHub repository webhook-co/webhook (0 stars, last pushed 18d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 439 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-31.
Other commands, from other repositories
local
Command "local" from getsentry/toolkit, covering sentry local run, browser ui, endpoints, tail output and agent tracing.
auth
Bare sentry auth logs in when you're logged out and shows status when you're already authenticated. sentry auth login always starts the login flow.
debug-files
Command "debug-files" from getsentry/toolkit, covering notes on find and important notes.
feedback
Modern User Feedback is stored as Feedback issues. sentry feedback list always limits issue searches to issue.category:feedback; it does not use the legacy User Reports API.
release
A typical CI release creates the release, associates commits, finalizes it, and records a deploy. The sentry release create examples above show the full sequence.
trace
With trace view --json --fields, summary fields such as traceId and duration select trace metadata. Bare attribute names such as http.method request that attribute on every span and return it under each span's additionalattributes. The output retains spanid and children so that attributes on nested spans stay…