Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-codeWrote 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/pwdev-solucoes/pwdev-claude-marketplace/execute)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/execute"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/execute.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.1 | $0.00011 | $0.02247 |
| Opus 5 | $0.00005 | $0.01123 |
| Sonnet 5 | $0.00002 | $0.00449 |
| Haiku 4.5 | $0.00001 | $0.00225 |
Grade A, and why
execute 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 6d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:execute — Execute Phase
Role (orchestrator — you do NOT implement; the executor subagent does)
You coordinate the execution loop: pick the next task, spawn a fresh
pwdev-code:executor subagent for it with a self-contained prompt, collect
its short status, update state.md, and move on. Each task runs in a fresh
context — this is the Fresh Context Model, for real.
Entry Gate
[ -d ".planning/phases/" ] || { echo "❌ No phases folder. Run /pwdev-code:design first."; exit 1; }
ls .planning/phases/*/plans/*.md >/dev/null 2>&1 || { echo "❌ No plans found. Run /pwdev-code:plan first."; exit 1; }
If .planning/state.md contains review_gate: BLOCKED and you are NOT
running --fix → warn that review found critical findings and they should be
addressed first.
Flow
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 0.5 — Uncommitted Work Check
git status --short 2>/dev/null
If uncommitted code is detected → warn the human before spawning anything:
- PT-BR:
⚠️ Codigo nao commitado detectado. Deseja commitar antes de continuar? (s/n) - EN:
⚠️ Uncommitted code detected. Commit before continuing? (y/n)
(Older versions generated an executor-context.md for stale sessions —
no longer needed: every spawn is fresh and self-contained by design.)
STEP 1 — Build the Work Queue
cat .planning/state.md
ls .planning/phases/*/plans/*.md
- Normal mode: pending plans, grouped by their
Wave:header, respectingDepends on:. Honor--plan=PP/--wave=Nfilters. --fixmode: the queue is.planning/phases/{slug}/verify/fix-*.md. Readfix_iterationfromstate.md(default 0). Iffix_iteration >= 2→ STOP: present both verify reports' diff to the human and escalate — do not loop forever. Otherwise increment it instate.md.
STEP 2 — Execution Loop (per task, wave by wave)
For each task of the current wave, in order:
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.
- 6d ago First seen · 179 lines · 11 tokens per session scan A 63fb521e03a8
execute is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 17d ago), licensed Apache-2.0. It adds 11 tokens to every session and 2,247 once invoked, about $0.0001 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.