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 feat-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/feat-quick)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-quick"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-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/feat-quick"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-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.00107 | $0.00674 |
| Opus 5.5 | $0.00043 | $0.00270 |
| Sonnet 5.5 | $0.00021 | $0.00135 |
| Haiku 4.5 | $0.00011 | $0.00067 |
Grade A, and why
feat-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 27d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick task (no plan file)
Procedure
- Language — resolve
lang(references/language.md). - Assess (silent) — read the project instructions file (
references/project-files.md) and.planning/feat/codebase.mdif present. Eligible only if ≤5 files and no architectural decision, schema migration or new UI flow; otherwise say which skill to use and stop. - Mini-plan (gate) — present and wait for approval:
📋 Quick Task Objective: {1 sentence} Files: {list with action} Approach: {2-3 sentences} Verification: {real command(s)} Proceed? (y/n) - Implement following the project conventions. Anything unexpected (a 6th file, a dependency, a design decision) → stop and escalate to the right planning skill.
- Verify — the commands declared in the project instructions file (Commands/Quality);
otherwise detect the toolchain and run its lint + tests. Never chain unrelated toolchains
with
||. UI change → verify it withplaywright-cliin the sessionfeat-quick, run from a scratch evidence directory outside the project, when available (references/testing.md); recordNOT_RUNotherwise. Before committing,git status --porcelainmust show only the approved files — delete tool side effects, never commit them. - Commit only the files of the approved mini-plan, with a Conventional Commit, after lint and tests pass. On the default branch, ask first.
- Record (audit on):
sh "<plugin-root>/scripts/audit-log.sh" event quick "" completed <commit> "<files>". - Result:
✅ Quick task complete Done: {what changed} Verification: {command → exit code} Commit: {hash} {message}
Prohibitions
- Never execute without mini-plan approval.
- Never touch more than 5 files — escalate instead.
- Never commit without lint + tests passing.
Language: resolve lang per references/language.md before any human-facing output. Safety: never read or expose .env* (except .env.example/.template/.sample), keys, certificates or credentials — references/safety.md. Paths references/, scripts/, templates/, schemas/ are relative to the plugin root (references/runtime.md).
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.
- 27d ago First seen · 57 lines · 107 tokens per session scan A fef6a199db0a
feat-quick 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 107 tokens to every session and 674 once invoked, about $0.0004 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-28.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.