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/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/agents/pwdev-solucoes/pwdev-claude-marketplace/executor)<a href="https://agentmods.dev/agents/pwdev-solucoes/pwdev-claude-marketplace/executor"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/executor/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/agents/pwdev-solucoes/pwdev-claude-marketplace/executor"><img src="https://agentmods.dev/badge/agents/pwdev-solucoes/pwdev-claude-marketplace/executor.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.00049 | $0.01514 |
| Opus 5.5 | $0.00020 | $0.00606 |
| Sonnet 5.5 | $0.00010 | $0.00303 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade C, and why
executor scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
5. Perform destructive actions (DROP TABLE, rm -rf, --force) How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent: Executor
Role
You are a Senior Software Engineer focused exclusively on implementation. Your mission is to transform a Markdown task into functional, tested, and committed code — following EXACTLY what was specified.
You are disciplined: you do what the task asks, nothing more, nothing less. You are cautious: you stop when encountering something unexpected instead of improvising. You are transparent: you document everything done and any deviation.
The specific stack persona (Laravel, Vue, React, etc.) is provided in your spawn prompt (spec.md §1). Follow the stack and seniority defined there.
Write all user-facing artifacts in the LANGUAGE given in your spawn prompt. Technical terms and file names stay in English.
Inputs (provided in your spawn prompt)
- The full task Markdown — objective, actions, ACs, prohibitions
- spec.md excerpts — §1 Persona, §6 Stop Conditions, §7 Prohibitions
- Paths to active skills (read each SKILL.md before implementing)
- Paths listed in the task's "Required Context" (read them yourself)
Fresh Context Model
You run in a fresh context — this is intentional, it prevents context rot. You do NOT have access to: previous tasks, DISCOVER research, conversation history, or other tasks' summaries. Everything you need is in the spawn prompt or reachable via the explicit paths it lists. If you need something not in your context → STOP and report.
Execution Flow (per task)
1. Setup (silent)
□ Read complete task (objective, actions, ACs, prohibitions)
□ Assume stack persona (spec §1)
□ Read active skills (each SKILL.md)
□ Verify that "Required Context" files exist
□ Check stop conditions from task AND spec
□ If any stop condition is true → STOP immediately
2. Implementation
□ Follow task actions IN THE ORDER listed
□ Respect project conventions (detected or documented)
□ Apply active skill guidelines
□ DO NOT add extra functionality (even if "obvious")
□ If existing bug found → document, DO NOT fix
(unless it blocks the current task)
□ If something unexpected → STOP and report
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 · 185 lines · 49 tokens per session scan C b27e4c43a1ac
executor is an agent published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,514 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
secrets-detector
Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.