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-featWrote 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/exec)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/exec"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/exec.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.00020 | $0.01301 |
| Opus 5 | $0.00010 | $0.00651 |
| Sonnet 5 | $0.00004 | $0.00260 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
exec 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-feat:exec — Execute Plan
Role (orchestrator — you do NOT implement; the executor subagent does)
Load the plan, detect the mode, spawn ONE fresh pwdev-feat:executor via the
Task tool with a self-contained prompt, collect its ≤10-line status, present it.
Input
$ARGUMENTS: feature slug (e.g., "user-crud") or "latest".
Flow
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 1 — Load Plan
if [ "$ARGUMENTS" = "latest" ] || [ -z "$ARGUMENTS" ]; then
FEATURE_DIR=$(ls -td .planning/feat/features/*/ 2>/dev/null | while read dir; do [ ! -f "$dir/plan.done.md" ] && echo "$dir" && break; done)
PLAN="${FEATURE_DIR}plan.md"
else
FEATURE_DIR=".planning/feat/features/${ARGUMENTS}/"
PLAN="${FEATURE_DIR}plan.md"
fi
if [ -z "$FEATURE_DIR" ] || [ ! -f "$PLAN" ]; then
echo "PLAN_NOT_FOUND"
else
grep -m1 '\*\*Type:\*\*' "$PLAN"
[ -f "${FEATURE_DIR}plan.done.md" ] && echo "ALREADY_EXECUTED"
cat "$PLAN"
fi
PLAN_NOT_FOUND→ show the create-plan hints and STOP — do not spawn:❌ No plan found. Create one first: /pwdev-feat:feat 'description' | /pwdev-feat:backend ... | /pwdev-feat:frontend ...ALREADY_EXECUTED→ warn and ask whether to re-run before continuing.
STEP 1.5 — Detect Mode
Per the mode rule in ${CLAUDE_PLUGIN_ROOT}/references/spawn-contracts.md:
Type review → MODE: REPORT; otherwise, Output Format with no code files
to create/modify (report-only) → MODE: REPORT; else → MODE: IMPLEMENT.
STEP 1.7 — Project Memory (optional, read-only)
If .planning/memory/MEMORY.md exists (curated by pwdev-code — pwdev-feat
NEVER writes there), read ONLY that index. Select ≤3 entries by keyword
overlap with the plan's scope (convention first; expand 1 hop via the
[rel: ...] suffixes within the cap of 3). Build a RELEVANT MEMORY block
with descriptions + file paths (spawn-contracts template). No match or no
index → omit the block entirely.
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.
- 3d ago First seen · 121 lines · 20 tokens per session scan A 4c5ba22ed49c
exec is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 1,301 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-09-03.
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
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.