A test-planning workflow for existing code, covering unit tests, integration tests, and end-to-end tests. End-to-end tests check a complete user flow, such as logging in through a web interface.

Use it to plan tests for a service or feature, design Playwright browser scenarios, or audit which parts of the code lack coverage.

It turns a testing request or coverage review into a documented plan instead of making untracked changes. It also records which behaviours each planned test should cover.

feat-test — Skill for Claude Code and Codex by pwdev-solucoes

Install

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.

Any agent

npx skills add pwdev-solucoes/pwdev-claude-marketplace --skill feat-test

Clone the repo

git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplace

Made for: Claude Code, Codex.

Or install pwdev-feat, the plugin that ships this one along with the rest of its 13 skills, 8 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-test/github.svg)](https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-test)

Your own site

<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-test"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-test/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-test"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 757 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00757
Opus 5.5	$0.00043	$0.00303
Sonnet 5.5	$0.00021	$0.00151
Haiku 4.5	$0.00011	$0.00076

Measured 27d ago against content hash 28f787efb6c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feat-test 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.

plugins/pwdev-feat/skills/feat-test/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test plan

Plan type test. You run in the MAIN session and interview the human. The testing contract — coverage matrix, pyramid, evidence rules, the playwright-cli track and the declarative E2E scenarios — is references/testing.md; read it before planning.

Procedure

Language — resolve lang (references/language.md).
Read the code under test first, plus context/testing.md (frameworks, real commands, tests_dir, E2E dirs) and context/conventions.md. No testing context → suggest feat-map.
Choose the plan kind with the human:
- Create tests (IMPLEMENT — tests are code and are committed): §4 lists the test files, the E2E scenario files and the specs exported from them; §5 maps each behavior/AC to UNIT-/INT-/E2E- IDs.
- Audit coverage (REPORT): §4 lists only .planning/feat/features/{slug}/test-audit.md, rendered from templates/test-report.md (not report.md: some runtimes refuse subagent writes to report-like names).
Method — follow references/pwdevia-method.md with plan_type: test.
Focus
- Persona: QA engineer / test specialist on the project's frameworks.
- Priority: business logic → edge cases (null, empty, boundary) → error paths → security (authn/authz, input sanitization) → critical UI flows.
- Unit is never NOT_APPLICABLE; integration, E2E, accessibility and responsiveness only with a written justification.
- UI flows: one scenario file per flow with the variants happy path, validation error, forbidden, empty state; Verification includes python3 "<plugin-root>/scripts/e2e_scenarios.py" validate <scenarios-dir> --plan <plan.md> and the export --to playwright command into <tests-dir>/e2e/generated.
- Interactive UI checks use playwright-cli in the session feat-{slug}, run from the feature's evidence/ directory, with one screenshot per UI criterion.

Prohibitions

Never skip E2E scenarios when the code under test has UI.
Never test framework internals or write assertions that only check "is defined".
Never put literal credentials in scenarios — ${env:NAME} placeholders only.

Read the full file on GitHub · 52 lines

Files

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.

agents/openai.yaml 183 B

Changes

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 · 52 lines · 107 tokens per session scan A 28f787efb6c3

Subscribe to this mod's changes

feat-test 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 757 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.

E2E testing Testing Unit testing

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

axiom-testing

Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.

CharlesWiltgen/Axiom · 38 tokens

designing-tests

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

CloudAI-X/claude-workflow-v2 · 48 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

JMeter Load Testing

Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.

PramodDutta/qaskills · 32 tokens

06-test

Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…

ai-driven-dev/framework · 69 tokens