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 agentmods add skills/whitewhiteqq/aws-test-plugin/aws-perf-load-testingnpx skills add whitewhiteqq/aws-test-plugin --skill aws-perf-load-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-perf-load-testing)<a href="https://agentmods.dev/skills/whitewhiteqq/aws-test-plugin/aws-perf-load-testing"><img src="https://agentmods.dev/badge/skills/whitewhiteqq/aws-test-plugin/aws-perf-load-testing.svg" alt="Measured on agentmods" 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.00103 | $0.01581 |
| Opus 5 | $0.00051 | $0.00790 |
| Sonnet 5 | $0.00021 | $0.00316 |
| Haiku 4.5 | $0.00010 | $0.00158 |
Grade A, and why
aws-perf-load-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 5d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Performance & Load Testing Skill
Generate benchmarks and load tests by reading handler code and API specs.
Performance Tests (pytest-benchmark + tracemalloc)
Phase 1: Build Realistic Events
Read the handler code to understand:
- What event shape does it expect? (API GW proxy, S3, SQS, direct)
- What are the hot paths? (most common code branches)
- What external calls does it make? (need to mock for benchmarks)
Phase 2: Generate Benchmark Tests
See references/benchmark-patterns.md for full patterns.
"""Performance benchmarks for {handler_name}."""
import json
import pytest
from unittest.mock import patch, MagicMock
pytestmark = pytest.mark.performance
@pytest.fixture
def mock_context():
ctx = MagicMock()
ctx.function_name = "test-function"
ctx.memory_limit_in_mb = 256
ctx.get_remaining_time_in_millis.return_value = 30000
return ctx
class TestHandlerLatency:
"""Benchmark handler execution time."""
def test_get_request_latency(self, mock_context, benchmark):
# Mock external dependencies so we measure handler logic only
with patch("handler.main.boto3") as mock_boto:
mock_boto.client.return_value.get_object.return_value = {
"Body": MagicMock(read=lambda: b'{"data": "value"}')
}
from handler.main import lambda_handler
event = {
"httpMethod": "GET",
"pathParameters": {"id": "bench-123"},
"headers": {"x-api-key": "test"},
}
result = benchmark(lambda_handler, event, mock_context)
assert result["statusCode"] == 200
def test_post_request_latency(self, mock_context, benchmark):
with patch("handler.main.boto3") as mock_boto:
mock_boto.client.return_value.put_item.return_value = {}
from handler.main import lambda_handler
event = {
"httpMethod": "POST",
"body": json.dumps({"name": "Benchmark"}),
"headers": {"x-api-key": "test"},
}
result = benchmark(lambda_handler, event, mock_context)
assert result["statusCode"] in (200, 201)
class TestMemoryUsage:
"""Profile handler memory consumption."""
def test_memory_within_limit(self, mock_context):
import tracemalloc
tracemalloc.start()
with patch("handler.main.boto3"):
from handler.main import lambda_handler
event = {"httpMethod": "GET", "pathParameters": {"id": "mem-test"}}
lambda_handler(event, mock_context)
current, peak = tracemalloc.get_traced_memory()
tracemalloc.stop()
peak_mb = peak / 1024 / 1024
limit_mb = mock_context.memory_limit_in_mb
assert peak_mb < limit_mb * 0.8, (
f"Peak {peak_mb:.1f}MB is >80% of {limit_mb}MB limit"
)
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.
- 5d ago First seen · 200 lines · 103 tokens per session scan A 99b15678915d
aws-perf-load-testing is a skill published in the GitHub repository whitewhiteqq/aws-test-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,581 once invoked, about $0.0005 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…