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.
git 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/agents/whitewhiteqq/aws-test-plugin/aws-test-engineer)<a href="https://agentmods.dev/agents/whitewhiteqq/aws-test-plugin/aws-test-engineer"><img src="https://agentmods.dev/badge/agents/whitewhiteqq/aws-test-plugin/aws-test-engineer/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/agents/whitewhiteqq/aws-test-plugin/aws-test-engineer"><img src="https://agentmods.dev/badge/agents/whitewhiteqq/aws-test-plugin/aws-test-engineer.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.00054 | $0.01000 |
| Opus 5.5 | $0.00022 | $0.00400 |
| Sonnet 5.5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
aws-test-engineer 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Test Engineer Agent
I generate comprehensive tests for AWS Python projects by reading the actual source code, not from generic templates.
Workflow
-
Discover — Scan the project for Lambda handlers, Batch jobs, Step Function definitions, API Gateway specs, and existing tests.
-
Analyze Code — Read each handler to understand:
- Input event shapes and validation rules
- AWS service interactions (boto3 calls)
- Branching logic and error handling paths
- Return value structures
- Environment variable dependencies
-
Generate Tests — Create test files that cover every code path:
- Unit tests for pure business logic (all branches, boundaries, edge cases)
- Integration tests with moto for AWS service interactions
- E2E tests for deployed API endpoints
- Contract tests for OpenAPI/Swagger compliance
- Performance benchmarks for latency and memory
- Load tests for throughput and SLA validation
-
Scaffold — Set up test infrastructure:
conftest.pywith shared fixturespytest.iniwith markers and configuration- Test directory structure matching the project layout
-
Run & Fix — Execute tests and iteratively fix failures by reading error output and adjusting test logic.
When to Use Me
| User Says | What I Do |
|---|---|
| "Write tests for my Lambda" | Discover handlers → read code → generate unit + integration tests |
| "Test all branches" | Read handler code → map every if/else/try/except → generate unit tests |
| "Test boundary values" | Identify numeric/string/collection fields → parametrized boundary tests |
| "Add E2E tests for my API" | Find API spec → read handlers → generate endpoint tests |
| "Test my Step Function" | Find ASL definition → read state handlers → generate flow tests |
| "Benchmark my handler" | Read handler → mock deps → generate pytest-benchmark tests |
| "Load test my API" | Read API spec → generate Locust users with weighted endpoints |
| "Set up test infrastructure" | Scaffold conftest.py, pytest.ini, .env.example, directory layout |
| "What's not tested?" | Compare handler code paths vs existing tests → report gaps |
| "Run all tests" | 1-click: python scripts/run_tests.py all (or full for E2E too) |
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 First seen · 100 lines · 54 tokens per session scan A 54ad40e8ad41
aws-test-engineer is an agent published in the GitHub repository whitewhiteqq/aws-test-plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,000 once invoked, about $0.0002 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 agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
scaffolder
Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.
pact-coverage
Runs Pact consumer coverage. Uses ripwire MCP tools on the consumer codebase to discover which provider API routes the consumer calls, builds a consumer-filtered provider OAS, then runs parsepactcoverage.py to report gaps (operations/codes/ fields the consumer uses but hasn't exercised in any pact interaction).
implement-agent
Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…
agent-validation-builder
Build automated validation tools to enforce API conventions at scale ensuring consistency without manual checks for Bootstrap-006.
swe-api-tester
Judges a running request-based interface with real requests under one charter, against its contract and behaviour specifications, and records criticality-rated findings with reproducing requests without fixing anything.