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-test-orchestratorWrote 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-test-orchestrator)<a href="https://agentmods.dev/skills/whitewhiteqq/aws-test-plugin/aws-test-orchestrator"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-test-orchestrator/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-test-orchestrator"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-test-orchestrator.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.00090 | $0.03156 |
| Opus 5 | $0.00045 | $0.01578 |
| Sonnet 5 | $0.00018 | $0.00631 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade C, and why
aws-test-orchestrator scanned grade C with 1 finding 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 8d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- **AWS credentials**: use the default AWS profile (`~/.aws/credentials`) — accessed via `boto3` automatically How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Test Orchestrator
Master coordination skill. Discovers the project, delegates to category-specific skills.
Step 1: Discover Project Components
Before writing any test, map the project. Run these discovery steps.
Derive the Component Prefix
Every component gets a unique env var prefix to avoid collisions in monorepos. Derive it from the service directory name, uppercased with hyphens replaced by underscores:
| Directory | Prefix | Example Env Vars |
|---|---|---|
orders-api/ |
ORDERS_API |
ORDERS_API_BASE_URL, ORDERS_API_KEY |
processing-batch/ |
PROCESSING_BATCH |
PROCESSING_BATCH_BATCH_JOB_QUEUE |
order-processor/ |
ORDER_PROCESSOR |
ORDER_PROCESSOR_SFN_ARN |
notifications/ |
NOTIFICATIONS |
NOTIFICATIONS_QUEUE_URL |
Use this prefix consistently in .env.example, conftest.py fixtures, and
E2E test modules. See references/secrets-and-config.md.
Find Lambdas
Search for files named main.py, handler.py, app.py, or lambda_function.py
under directories that contain lambda, function, or handler in their path.
Each directory containing such a file is one Lambda function.
Record for each Lambda:
- Component prefix (derived from directory name)
- Directory path and handler file name
- Handler function name (look for
def lambda_handler,def handler, or the entry point) - Event source: API Gateway (has
httpMethod/requestContext), S3 (hasRecords[].s3), SQS (hasRecords[].body), SNS, EventBridge, direct invoke - AWS services used: scan imports for
boto3.client(...)orboto3.resource(...)— record each service name (s3, dynamodb, rds, stepfunctions, etc.) - Environment variables: scan for
os.environ[...]oros.getenv(...)calls - Validation: look for pydantic models, jsonschema, or manual validation logic
Find Batch Jobs
Search for directories containing Dockerfile, batch, or job in their name.
Look for the main entry point (main.py, run.py, app.py).
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.
- 8d ago First seen · 317 lines · 90 tokens per session scan C d4c6f004cf64
aws-test-orchestrator is a skill published in the GitHub repository whitewhiteqq/aws-test-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 90 tokens to every session and 3,156 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…