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.
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 aws-samples/sample-agent-skills-for-builders --skill create-install-scriptsgit 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/skills/aws-samples/sample-agent-skills-for-builders/create-install-scripts)<a href="https://agentmods.dev/skills/aws-samples/sample-agent-skills-for-builders/create-install-scripts"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-agent-skills-for-builders/create-install-scripts/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/aws-samples/sample-agent-skills-for-builders/create-install-scripts"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-agent-skills-for-builders/create-install-scripts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00437 |
| Opus 5.5 | $0.00018 | $0.00175 |
| Sonnet 5.5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
create-install-scripts 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 1mo 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
Create Install Scripts
Generate installation scripts, GitLab CI configuration, and CodeBuild deployment setup for AWS CDK projects.
When to Apply
Reference this skill when:
- Setting up deployment pipelines for CDK projects
- Creating interactive install.sh scripts
- Configuring GitLab CI/CD for AWS deployments
- Setting up AWS CodeBuild for Docker image builds
- Automating CDK deployment workflows
How It Works
- Analyze the CDK project structure
- Generate
install.shfor interactive local deployments - Generate
.gitlab-ci.ymlfor GitLab CI/CD - Generate
buildspec.ymlfor AWS CodeBuild - Configure deployment variables and secrets
Prerequisites
- AWS CDK project initialized
- GitLab repository (for CI/CD)
- AWS credentials configured
- Docker (if using CodeBuild for images)
Usage
# Run the setup script
./scripts/setup-cicd.sh
# Or trigger via agent
"Set up CI/CD for my CDK project"
"Create install scripts for deployment"
Generated Files
| File | Purpose |
|---|---|
install.sh |
Interactive installation script |
.gitlab-ci.yml |
GitLab CI/CD pipeline |
buildspec.yml |
AWS CodeBuild specification |
References
- Install Script Guide - Complete install.sh creation guide
- GitLab CI Setup - GitLab CI/CD configuration
- CodeBuild Setup - AWS CodeBuild setup
- Common Pitfalls - Troubleshooting guide
What ships with it
6 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.
- 1mo ago First seen · 63 lines · 44 tokens per session scan A 251e7f7a8139
create-install-scripts is a skill published in the GitHub repository aws-samples/sample-agent-skills-for-builders (53 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 437 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.