Sample Agent Skills for Builders is a collection of reusable skills that extend AI coding agents with AWS, CDK, security, testing, and engineering workflows. Developers can install the skills for practical AWS development tasks or use the repository as a model for creating their own agent skills. The catalogue entries are skills and instructions from this collection.
Borrowing it
Nothing to install: this file belongs to aws-samples/sample-agent-skills-for-builders. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aws-samples/sample-agent-skills-for-builders/main/CLAUDE.mdgit clone --depth 1 https://github.com/aws-samples/sample-agent-skills-for-buildersWrote 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/instructions/aws-samples/sample-agent-skills-for-builders/claude-md)<a href="https://agentmods.dev/instructions/aws-samples/sample-agent-skills-for-builders/claude-md"><img src="https://agentmods.dev/badge/instructions/aws-samples/sample-agent-skills-for-builders/claude-md.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.00384 | $0.00384 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
sample-agent-skills-for-builders CLAUDE.md 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 7d 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.
What it actually says
CLAUDE.md
Notes for Claude Code working inside this repository. For the general skill spec (frontmatter, directory layout, conventions), read AGENTS.md — this file only covers repo-local behaviors that agents need on top of the spec.
Repo shape
skills/<kebab-case-name>/SKILL.md— one skill per directory.skills/<name>/references/— long-form docs the skill pulls in on demand.skills/<name>/scripts/— automation the skill can invoke.AGENTS.md— canonical spec. Treat it as the source of truth over any loose conventions inferred from existing skills.
Useful one-liners
# list skills
ls skills/
# show every SKILL.md's frontmatter
for f in skills/*/SKILL.md; do echo "### $f"; awk '/^---$/{c++; next} c==1' "$f"; done
# find all section headings across skills (spot structural drift)
grep -nE '^## ' skills/*/SKILL.md
When creating a skill
Follow AGENTS.md exactly — including the template headings
(When to Apply, How It Works, Usage, References). Don't invent
alternative heading names; structural consistency across skills is a
feature of this repo.
When editing an existing skill
- Don't shorten the
descriptionfrontmatter field — it's the only text an agent sees at startup when deciding whether to load the skill, so richer trigger phrases help discovery. - Keep
SKILL.mdunder ~500 lines; move detail intoreferences/. - If you rename a section heading, grep for anchor links first:
grep -rn '#section-name' .
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.
- 7d ago First seen · 43 lines · 384 tokens per session scan A b09a5c82daf6
sample-agent-skills-for-builders CLAUDE.md is an instructions file published in the GitHub repository aws-samples/sample-agent-skills-for-builders (47 stars, last pushed 10d ago), licensed Apache-2.0. It adds 384 tokens to every session, about $0.0019 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.