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 whitewhiteqq/aws-test-plugin --skill aws-e2e-testinggit clone --depth 1 https://github.com/whitewhiteqq/aws-test-pluginWrote 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/whitewhiteqq/aws-test-plugin/aws-e2e-testing)<a href="https://agentmods.dev/skills/whitewhiteqq/aws-test-plugin/aws-e2e-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-e2e-testing/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/whitewhiteqq/aws-test-plugin/aws-e2e-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-e2e-testing.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.00073 | $0.02048 |
| Opus 5.5 | $0.00029 | $0.00819 |
| Sonnet 5.5 | $0.00015 | $0.00410 |
| Haiku 4.5 | $0.00007 | $0.00205 |
Grade A, and why
aws-e2e-testing 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS E2E Testing Skill
Generate comprehensive E2E tests by reading the handler code and producing tests that exercise every endpoint, workflow branch, and failure mode against a deployed environment.
How to Generate E2E Tests
Phase 1: Understand the System Under Test
- Read the handler source code — do NOT guess the API shape
- Read the OpenAPI/Swagger spec (if one exists) — get exact paths, methods, schemas
- Read CloudFormation/SAM templates — find API Gateway resource definitions, stage names
- Identify the full workflow — which Lambdas call which other services?
Phase 2: Map Code Paths to E2E Scenarios
For each endpoint or workflow, generate tests for:
| Code Pattern Found | E2E Test to Generate |
|---|---|
if httpMethod == "GET" |
test_get_resource_returns_200 |
if httpMethod == "POST" + validation |
test_create_resource_valid_payload_returns_200 |
| Validation with required fields | test_create_resource_missing_required_field_returns_400 |
| Authorization check | test_request_without_auth_returns_403 |
| Database lookup by ID | test_get_nonexistent_resource_returns_404 |
| try/except around DB call | test_get_resource_db_error_returns_500 |
| PUT with ID in body | test_update_resource_returns_200 |
| DELETE endpoint | test_delete_resource_returns_200_or_204 |
| Search/list with filters | test_search_with_valid_filter_returns_results |
| File upload handling | test_upload_file_returns_document_id |
| Async processing (Step Function) | test_async_request_returns_202_with_request_id |
| Pagination logic | test_list_with_pagination_returns_next_token |
Phase 3: Write the Tests
Follow these patterns — see references/api-gateway-patterns.md for API tests, references/step-function-patterns.md for workflow tests, and references/batch-patterns.md for batch tests.
What ships with it
3 files 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 · +1 lines c7106a02d9a3
- 1mo ago First seen · 203 lines · 73 tokens per session scan A b9490b1f544b
aws-e2e-testing is a skill published in the GitHub repository whitewhiteqq/aws-test-plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 2,048 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
dast-scanning
Perform dynamic application security testing with OWASP ZAP, Burp Suite, and Nikto. Test running applications for security vulnerabilities through automated and manual testing. Use when testing web applications, APIs, or performing penetration testing.
testing-patterns
Skill "testing-patterns" from seandkendall/kiro-config, covering testing patterns, python lambda test (pytest + moto), react component test (vitest + rtl), coverage commands and playwright quick reference.
selenium-ui-test-generator
Generates Selenium WebDriver tests for React/Angular front-ends with STRICT loop prevention. Triggers on: "test UI", "generate Selenium tests", "test React app", "create E2E tests", "test front-end". WARNING: UI tests cost 3x more than unit tests -- generate selectively.
webapp-testing
Toolkit for testing local web applications and browser workflows with MCP browser tools. Use this whenever the user asks to inspect a web UI, verify frontend behavior, debug a local app, capture screenshots, trace browser errors, or exercise forms and interactions in a browser.
aws-testing
Testing strategies for AWS workloads. Use when writing unit tests, integration tests, contract tests, mocking AWS services, or setting up quality gates and CI/CD test pipelines.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.