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 medy-gribkov/arcana --skill aws-essentialsgit clone --depth 1 https://github.com/medy-gribkov/arcanaWrote 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/medy-gribkov/arcana/aws-essentials)<a href="https://agentmods.dev/skills/medy-gribkov/arcana/aws-essentials"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/aws-essentials/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/medy-gribkov/arcana/aws-essentials"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/aws-essentials.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.00036 | $0.04609 |
| Opus 5 | $0.00018 | $0.02305 |
| Sonnet 5 | $0.00007 | $0.00922 |
| Haiku 4.5 | $0.00004 | $0.00461 |
Grade A, and why
aws-essentials 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 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.
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 — 638 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Essentials
Production-ready patterns for AWS core services: Lambda handlers, S3 operations, RDS connection management, IAM policies, async messaging, DynamoDB design, CloudFront caching, and cost optimization.
Lambda Handler Patterns
BAD: Unoptimized cold starts, no reuse
// TypeScript - AWS SDK v3
import { DynamoDBClient, PutItemCommand } from '@aws-sdk/client-dynamodb';
export const handler = async (event: any) => {
const client = new DynamoDBClient({ region: 'us-east-1' }); // ❌ Created every invocation
const apiKey = 'hardcoded-key-abc123'; // ❌ Hardcoded credentials
await client.send(new PutItemCommand({
TableName: 'users',
Item: { id: { S: event.id }, data: { S: JSON.stringify(event) } }
}));
};
GOOD: Warm reuse, environment config, structured logging
import { DynamoDBClient, PutItemCommand } from '@aws-sdk/client-dynamodb';
import { SecretsManagerClient, GetSecretValueCommand } from '@aws-sdk/client-secrets-manager';
// ✅ Instantiate outside handler for reuse across warm invocations
const dynamoClient = new DynamoDBClient({ region: process.env.AWS_REGION });
const secretsClient = new SecretsManagerClient({ region: process.env.AWS_REGION });
let cachedSecret: string | null = null;
async function getSecret(): Promise<string> {
if (cachedSecret) return cachedSecret;
const response = await secretsClient.send(
new GetSecretValueCommand({ SecretId: process.env.SECRET_ARN })
);
cachedSecret = response.SecretString!;
return cachedSecret;
}
export const handler = async (event: { id: string; data: Record<string, any> }) => {
const startTime = Date.now();
try {
const secret = await getSecret();
await dynamoClient.send(new PutItemCommand({
TableName: process.env.TABLE_NAME!,
Item: {
id: { S: event.id },
data: { S: JSON.stringify(event.data) },
timestamp: { N: Date.now().toString() }
}
}));
console.log(JSON.stringify({
level: 'info',
message: 'Item stored',
id: event.id,
duration: Date.now() - startTime
}));
return { statusCode: 200, body: JSON.stringify({ success: true }) };
} catch (error) {
console.error(JSON.stringify({
level: 'error',
message: 'Failed to store item',
error: error instanceof Error ? error.message : String(error),
id: event.id
}));
throw error;
}
};
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 · 638 lines · 36 tokens per session scan A 4d6d32523fd7
aws-essentials is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 4,609 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
aws-architect
Design AWS architectures — VPCs, EC2, ECS, Lambda, RDS, S3, CloudFront, and Well-Architected Framework reviews.
azure-architect
Design Azure architectures — AKS, Functions, Cosmos DB, Service Bus, and Azure AD integration patterns.
gcp-architect
Design Google Cloud architectures — GKE, Cloud Run, BigQuery, Pub/Sub, and Cloud Spanner solutions.
n8n-workflow
Build n8n automation workflows — nodes, expressions, error handling, and self-hosted deployment.
terraform-writer
Write Terraform infrastructure-as-code — providers, modules, state management, and cloud resource definitions.
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.