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.
npx skills add pwdev-solucoes/pwdev-claude-marketplace --skill power-executegit 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/skills/pwdev-solucoes/pwdev-claude-marketplace/power-execute)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-execute"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-execute/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/skills/pwdev-solucoes/pwdev-claude-marketplace/power-execute"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-execute.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.00029 | $0.01657 |
| Opus 5.5 | $0.00012 | $0.00663 |
| Sonnet 5.5 | $0.00006 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
power-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 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute a Plan, Task by Task
Two rules hold for the whole session: every gate is human, and a subagent's report never gets pasted into your context — you read its status and its path. Never edit the user's own configuration, never push, merge, or commit on a default branch unless the human asked. Read collaboration at a gate or when a status comes back, runtime before the first dispatch, and safety before any git or destructive operation.
You are the controller. You dispatch, you adjudicate, you record. You do not implement and you do not fix. The moment you edit code yourself, every discipline below stops applying to that edit.
Setup
-
Ensure isolation with
pwdev-power:power-worktree. -
../../scripts/power-workspace.sh <slug>prints the working directory and createsledger.md. -
Read the ledger. Its first line names its plan. Tasks marked
Task NN: completeare done — do not dispatch them again. A ledger belonging to a different plan is not yours; ignore it.This check exists because the most expensive observed failure is a controller that lost its place and re-dispatched a whole sequence of finished tasks.
-
Pre-flight scan, before Task 01. Produce a table with one row per pair of tasks that share a file or an interface — what one produces against what the other consumes — and one row per task confirming its own text agrees with itself. Record every ruling you make in the ledger. "The scan is clean" without those rows is not a scan you ran.
Model selection
- Codex inherits host or session model and reasoning-effort settings; override only for an explicit instruction, governance rule, configuration, or approved profile, after confirming a supported model-and-effort combination on that host.
- Claude Code keeps explicit model routing on every dispatch: read
model-profiles before choosing, and apply the configured
profile to the task's declared
Complexitywith a model the runtime supports. - Hermes Agent follows hermes-tools; never invent model, provider, or effort parameters.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +3 lines 5031ddd1f59e
- 1mo ago Changed · +10 lines dc50068d5824
- 1mo ago First seen · 141 lines · 29 tokens per session scan A 32e4240ab1c3
power-execute is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,657 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…