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/eliecer2000/kiro-bootstrap/aws-testingnpx skills add eliecer2000/kiro-bootstrap --skill aws-testinggit clone --depth 1 https://github.com/eliecer2000/kiro-bootstrapWrote 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/eliecer2000/kiro-bootstrap/aws-testing)<a href="https://agentmods.dev/skills/eliecer2000/kiro-bootstrap/aws-testing"><img src="https://agentmods.dev/badge/skills/eliecer2000/kiro-bootstrap/aws-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 | $0.00036 | $0.02236 |
| Opus 5 | $0.00018 | $0.01118 |
| Sonnet 5 | $0.00007 | $0.00447 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
aws-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 4d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Testing
Skill para estrategias de testing en workloads AWS: pruebas unitarias, integración, contratos, end-to-end, property-based testing, mocking de servicios AWS y quality gates en CI/CD.
Principios fundamentales
- Test pyramid: muchos unit tests, algunos integration tests, pocos E2E tests.
- Lógica de negocio siempre testeable sin AWS: separar handler de service de repository.
- Mocks para unit tests, servicios reales (o LocalStack/DynamoDB Local) para integration tests.
- Cada PR debe pasar quality gates: tests, linting, type checking, coverage mínimo.
- Property-based testing para validar invariantes y encontrar edge cases que los tests manuales no cubren.
Pirámide de testing para serverless
┌─────────┐
│ E2E │ Pocos: flujos críticos contra stack desplegado
├─────────┤
│ Integr. │ Algunos: Lambda + DynamoDB Local, API contracts
├─────────┤
│ Unit │ Muchos: lógica de negocio pura, sin AWS
└─────────┘
Unit testing
Python con pytest
import pytest
from unittest.mock import MagicMock
from functions.orders.service import OrderService
@pytest.fixture
def mock_repo():
return MagicMock()
def test_create_order_success(mock_repo):
mock_repo.save.return_value = None
service = OrderService(mock_repo)
result = service.create({"item": "laptop", "quantity": 1, "price": 999.99})
assert result["status"] == "created"
mock_repo.save.assert_called_once()
def test_create_order_invalid_quantity(mock_repo):
service = OrderService(mock_repo)
with pytest.raises(ValueError, match="quantity must be positive"):
service.create({"item": "laptop", "quantity": 0, "price": 999.99})
TypeScript con Vitest
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { OrderService } from './service';
describe('OrderService', () => {
const mockRepo = { save: vi.fn(), findById: vi.fn() };
beforeEach(() => vi.clearAllMocks());
it('should create order successfully', async () => {
mockRepo.save.mockResolvedValue(undefined);
const service = new OrderService(mockRepo);
const result = await service.create({ item: 'laptop', quantity: 1, price: 999.99 });
expect(result.status).toBe('created');
expect(mockRepo.save).toHaveBeenCalledOnce();
});
it('should reject invalid quantity', async () => {
const service = new OrderService(mockRepo);
await expect(service.create({ item: 'laptop', quantity: 0, price: 999.99 }))
.rejects.toThrow('quantity must be positive');
});
});
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.
- 4d ago First seen · 271 lines · 36 tokens per session scan A 8456b2d08dbd
aws-testing is a skill published in the GitHub repository eliecer2000/kiro-bootstrap (9 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 2,236 once invoked, about $0.0002 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
cognito-passkey-auth
Amazon Cognito — Custom UI with Passkeys, Social Login & Face ID. Reference skill (loaded via skill:// from the ios agent).
amazon-location-service
Amazon Location Service. Reference skill (loaded via skill:// from the ios agent).
amazon-polly-generative
Amazon Polly Generative Voices. Reference skill (loaded via skill:// from the ios agent).
verify-rule
Use when verifying a CSS noop rule against real Chromium behavior, checking rule correctness and e2e/unit test consistency. Triggers on "verify rule", "check rule", "re-verify", or reviewing rule accuracy after changes.
amazon-bedrock
Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore. Use when invoking models, setting up Knowledge Bases, creating agents, applying guardrails, deploying to AgentCore, troubleshooting Bedrock…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.