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/simplify)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/simplify"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/simplify.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.00018 | $0.00953 |
| Opus 5 | $0.00009 | $0.00477 |
| Sonnet 5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
simplify 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:simplify — Code Simplification Pass
Role (orchestrator — the simplifier subagent does the work)
Optional quality step between EXECUTE and REVIEW: reuse, dead-code removal, complexity reduction, efficiency. It is NOT a bug hunt (that is /review's job) and it never changes behavior. Two passes: ANALYZE (propose) → human approves by ID → APPLY (implement + refactor commit).
Entry Gate
ls .planning/phases/*/execution/*-summary.md >/dev/null 2>&1 || [ -n "$ARGUMENTS" ] || { echo "❌ No execution summaries and no explicit scope. Run /pwdev-code:execute first or pass files/--diff."; exit 1; }
Flow
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 1 — Determine Scope
$ARGUMENTSgiven → use it (file list or--diff HEAD~N).- Default → the phase's execution commits: read
state.mdfor the active phase, resolve the commit range since the phase's first execute commit (git log --oneline+ summaries' commit hashes).
STEP 2 — Gather Spawn Inputs
For the prompts only (do not analyze yourself): spec.md §5 (Quality) and §7
(Prohibitions) of the active phase; RELEVANT MEMORY block per
${CLAUDE_PLUGIN_ROOT}/references/memory.md (conventions first);
project verification commands (CLAUDE.md §12/§14).
STEP 3 — Spawn ANALYZE
Via the Task tool:
subagent_type:pwdev-code:simplifiermodel: resolve per${CLAUDE_PLUGIN_ROOT}/references/model-profiles.md- prompt: ANALYZE template in
${CLAUDE_PLUGIN_ROOT}/references/spawn-contracts.md. - Log the resolved model right after spawning:
"${CLAUDE_PLUGIN_ROOT}/scripts/audit-log.sh" spawn simplify SIMPLIFY pwdev-code:simplifier <model>
Log: "${CLAUDE_PLUGIN_ROOT}/scripts/audit-log.sh" event simplify SIMPLIFY simplify_proposed simplify-proposals.md '{"count":N}'
STEP 4 — Human Approval by ID
Present the proposals table from the status reply + report path. Ask: approve all / none / list of IDs (e.g. "S1, S3").
STATUS: NOTHING_TO_PROPOSEor 0 approved → end cleanly:✨ Nothing to simplify (or nothing approved). Code stays as is. 👉 Next: /pwdev-code:review
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.
- 8d ago First seen · 85 lines · 18 tokens per session scan A c6afe66fc71c
simplify is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 953 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.