Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/whitewhiteqq/aws-test-pluginnpx agentmods add skills/whitewhiteqq/aws-test-plugin/aws-unit-testingWrote 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-unit-testing)<a href="https://agentmods.dev/skills/whitewhiteqq/aws-test-plugin/aws-unit-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-unit-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-unit-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-unit-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.00108 | $0.04808 |
| Opus 5.5 | $0.00043 | $0.01923 |
| Sonnet 5.5 | $0.00022 | $0.00962 |
| Haiku 4.5 | $0.00011 | $0.00481 |
Grade A, and why
aws-unit-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 — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Unit Testing Skill
Generate unit tests that cover every branch, boundary, and edge case in business logic by reading the actual source code.
Core Principle
Unit tests isolate business logic from AWS infrastructure. Mock all external dependencies (boto3, HTTP calls, database). Test the logic only.
How to Generate Unit Tests
Phase 1: Identify Business Logic
Read the handler source and separate concerns:
| Layer | What It Does | Unit Test? |
|---|---|---|
| Input parsing / validation | Extracts and validates fields | Yes |
| Business rules | Decisions, calculations, transformations | Yes |
| Data formatting / mapping | Converts between formats | Yes |
| AWS service calls | Reads/writes to S3, DynamoDB, etc. | No (integration test) |
| HTTP response building | Constructs status code + body | Yes |
| Error handling logic | Decides which error to return | Yes |
Phase 2: Map Every Branch
Read the code and create a branch map. Every control flow path needs a test:
Function: process_order(event)
├── if not event.get("body") → 400 missing body [test_1]
├── try: json.loads(body)
│ └── except JSONDecodeError → 400 invalid JSON [test_2]
├── if "order_id" not in data → 400 missing order_id [test_3]
├── if "amount" not in data → 400 missing amount [test_4]
├── if amount <= 0 → 400 invalid amount [test_5]
├── if amount > 10000 → 400 exceeds limit [test_6]
├── if currency not in SUPPORTED → 400 unsupported [test_7]
├── try: save_to_db(order)
│ ├── except ConditionalCheckFailed → 409 duplicate [test_8]
│ └── except ClientError → 500 internal error [test_9]
├── if notify_customer: send_notification() [test_10]
└── return 200 success [test_11]
Phase 3: Identify Boundaries
For every numeric, string, or collection parameter, test at the boundaries:
| Parameter Type | Boundary Values to Test |
|---|---|
| Integer/Float | 0, 1, -1, max-1, max, max+1, MIN_INT, MAX_INT |
| String | "", single char, max length, max+1, unicode, whitespace-only |
| List/Array | [], single element, max size, max+1 |
| Optional/None | None, missing key, empty string vs None |
| Date/Time | epoch, now, far future, leap day, DST boundary |
| Enum/Choice | each valid value, invalid value, case mismatch |
| Boolean | True, False, None, truthy/falsy values |
What ships with it
2 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 4649b038b66f
- 1mo ago First seen · 517 lines · 108 tokens per session scan A 92d4015a8568
aws-unit-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 108 tokens to every session and 4,808 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-08-31.
Other skills, from other repositories
component-tester
Run Vitest tests for a specific component with coverage. Use when making changes to React components to ensure tests pass and coverage is maintained.
dotnet-nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution.
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.
java-unit-test-generator
Generates JUnit unit tests for Java classes with loop prevention and incremental generation. Triggers on: "generate unit tests", "create JUnit tests", "test Java class", "add test coverage".
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.
python-runtime
Python toolchain configuration and best practices. Use when setting up Ruff, pytest, mypy type hints, dependency management, virtual environments or Python project standards.