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-quickgit 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-quick)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-quick"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-quick/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-quick"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-quick.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.00048 | $0.00517 |
| Opus 5 | $0.00024 | $0.00259 |
| Sonnet 5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
power-quick 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 6d 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.
What it actually says
Deliver a Bounded Change
Read collaboration and safety before acting.
The scope gate
This skill is for changes that are small and understood. Both, not either.
Escalate to pwdev-power:power-brainstorm the moment any of these is true:
- more than three files would change
- you cannot name the failure mode of the change
- it adds a new interface, dependency, or migration
- it touches auth, payments, permissions, or data deletion
- you are about to write "while I'm here"
Escalating is not failure. Discovering mid-change that this was never quick, and continuing anyway, is.
Steps
- Read before proposing. Read the actual files. A quick change proposed from memory of a
codebase is a guess.
.planning/power/context/project.md, if it exists, gives you the conventions without exploring — which is the whole point on a change this small. - Present a mini-plan: what changes, in which files, and how you will verify it. Three or four lines.
- Gate. Wait for a yes.
- Implement. If this is a bugfix,
pwdev-power:power-tddstill applies — a bug means a test was missing, and "it is only one line" is the most common way that test never gets written. - Verify. Run the real command, read the real output.
pwdev-power:power-verifystates the standard: evidence before the claim. - Commit with a message that says why, not what. The diff already says what.
Record
Write .planning/power/quick/<date>-<slug>/contract.md with the mini-plan you agreed to, and
report.md with what you did and the verification output. Two short files.
They exist because "quick" changes are the ones nobody can explain three months later, and because a pattern of quick changes to the same area is evidence that the area needs a real plan.
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.
- 6d ago First seen · 49 lines · 48 tokens per session scan A 69cb8e1c8a29
power-quick is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 48 tokens to every session and 517 once invoked, about $0.0002 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…