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-plangit 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-plan)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-plan"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-plan/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-plan"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-plan.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.00024 | $0.00868 |
| Opus 5 | $0.00012 | $0.00434 |
| Sonnet 5 | $0.00005 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
power-plan 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write an Executable Plan
Read artifacts, collaboration, context, and model-profiles before acting.
If no approved design exists, stop and use pwdev-power:power-brainstorm first. A plan
without a spec is a guess with numbered steps.
Read .planning/power/context/project.md and .planning/power/context/stack.md when they
exist. File Structure must
name paths that exist in this repository, and every verification step must use the project's real
commands — a plan step that runs npm test against a pytest project fails on the first task,
for the most avoidable reason there is.
Who you are writing for
An engineer who joins at this task, has none of your context, cannot see the conversation, and will not see the other tasks. Everything they need must be in their own task. Assume good faith and questionable taste: if a value can be misread, it will be.
Structure
# <Feature> — Plan
Status: DRAFT
Spec: .planning/power/features/<slug>/spec.md
Updated: <ISO date>
For agentic workers: execute this with pwdev-power:power-execute.
## Goal
## Architecture
## Tech Stack
## Global Constraints
<exact values copied verbatim from the spec — timeouts, limits, formats, names, versions>
## File Structure
<every file this plan creates or changes, decided here, before any task>
## Task 01 — <name>
Complexity: low | medium | high
Files: <exact paths>
Interfaces:
Consumes: <exact signatures from earlier tasks>
Produces: <exact signatures later tasks will consume>
Steps:
- [ ] Write a failing test for <behavior>
- [ ] Run it, watch it fail for the right reason
- [ ] Implement <the minimum that passes>
- [ ] Run it, watch it pass
- [ ] Commit
Global Constraints is copied verbatim, not summarized. The reviewer checks the
implementation against this block, so a paraphrase here becomes a wrong verdict there.
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.
- 8d ago First seen · 96 lines · 24 tokens per session scan A e2cded8e2beb
power-plan is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 868 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.