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-contract-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-contract-testing)<a href="https://agentmods.dev/skills/whitewhiteqq/aws-test-plugin/aws-contract-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-contract-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-contract-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-contract-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.00096 | $0.01217 |
| Opus 5.5 | $0.00038 | $0.00487 |
| Sonnet 5.5 | $0.00019 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00122 |
Grade A, and why
aws-contract-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 24d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Contract Testing Skill
Generate offline contract tests by reading OpenAPI specs, SAM templates, and CloudFormation definitions. No network calls needed.
How to Generate Contract Tests
Phase 1: Find the API Specification
Search the project for:
swagger.yml,swagger.yaml,openapi.yml,openapi.yaml,openapi.json- SAM
template.yamlwithAWS::Serverless::Api+ inline swagger - CloudFormation with
AWS::ApiGateway::RestApi+Bodyproperty api.jsonor any file containing"openapi"or"swagger"keys
Phase 2: Extract Schemas and Endpoints
From the spec, extract:
- All schemas under
components.schemas(ordefinitionsin Swagger 2) - All endpoints — method + path + request body schema + response schema
- Required fields for each schema
- Enum values for constrained fields
- Security schemes — API key, OAuth, IAM
- Global security requirements
Phase 3: Generate Contract Tests
See references/openapi-patterns.md for full patterns.
Schema Completeness Tests
"""Verify all expected schemas exist in the spec."""
import yaml
import pytest
from pathlib import Path
SPEC_PATH = Path("path/to/swagger.yml") # Discovered in Phase 1
@pytest.fixture(scope="module")
def spec():
return yaml.safe_load(SPEC_PATH.read_text(encoding="utf-8"))
@pytest.fixture(scope="module")
def schemas(spec):
return spec.get("components", spec.get("definitions", {})).get("schemas", {})
class TestSchemaCompleteness:
# Auto-populated from spec analysis:
EXPECTED_SCHEMAS = [
# List every schema name found in the spec
]
@pytest.mark.parametrize("schema_name", EXPECTED_SCHEMAS)
def test_schema_exists(self, schemas, schema_name):
assert schema_name in schemas, f"Missing schema: {schema_name}"
Request Validation Tests
For each endpoint with a request body:
from jsonschema import validate, ValidationError
class TestCreateResourceContract:
def test_valid_request_passes(self, schemas):
schema = schemas["createResourceRequest"]
payload = {
# All required fields with valid values
}
validate(instance=payload, schema=schema) # No error = pass
def test_missing_required_field_fails(self, schemas):
schema = schemas["createResourceRequest"]
with pytest.raises(ValidationError):
validate(instance={}, schema=schema)
def test_extra_field_accepted_or_rejected(self, schemas):
schema = schemas["createResourceRequest"]
payload = {
# Required fields + an extra unknown field
"unknownField": "value",
}
if schema.get("additionalProperties") is False:
with pytest.raises(ValidationError):
validate(instance=payload, schema=payload)
else:
validate(instance=payload, schema=schema) # Should pass
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.
- 24d ago Changed · +1 lines f699c103413c
- 1mo ago First seen · 167 lines · 96 tokens per session scan A df2c12d5e8a4
aws-contract-testing is a skill published in the GitHub repository whitewhiteqq/aws-test-plugin (2 stars, last pushed 25d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,217 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
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
pytest
Pytest testing patterns for Python. Trigger: When writing or refactoring pytest tests (fixtures, mocking, parametrize, markers). For Prowler-specific API/SDK testing conventions, also use prowler-test-api or prowler-test-sdk.
securing-api-gateway-with-aws-waf
Securing API Gateway endpoints with AWS WAF by configuring managed rule groups for OWASP Top 10 protection, creating custom rate limiting rules, implementing bot control, setting up IP reputation filtering, and monitoring WAF metrics for security effectiveness.
API Gateway Testing
API gateway testing skill covering rate limiting validation, request routing, authentication proxy testing, load balancing verification, circuit breaker testing, and gateway configuration validation for Kong, Envoy, and AWS API Gateway.
thousandeyes
ThousandEyes network intelligence integration for monitoring tests, alerts, agents, Internet Insights outages, dashboards, and BGP routes during RCA investigations.
rest-api-test-generator
Generates REST API tests using RestAssured or MockMvc with loop prevention and incremental validation. Triggers on: "test API endpoints", "generate API tests", "test REST API", "create integration tests".