aws-samples/serverless-samples is a collection of example code for serverless applications, where cloud services run application logic without developers managing servers directly. It helps developers learn how to build applications using services such as API Gateway and Lambda.
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/serverless-samples --skill code-standardsgit clone --depth 1 https://github.com/aws-samples/serverless-samplesWrote 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/serverless-samples/code-standards)<a href="https://agentmods.dev/skills/aws-samples/serverless-samples/code-standards"><img src="https://agentmods.dev/badge/skills/aws-samples/serverless-samples/code-standards/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/serverless-samples/code-standards"><img src="https://agentmods.dev/badge/skills/aws-samples/serverless-samples/code-standards.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.00000 | $0.00704 |
| Opus 5.5 | $0.00000 | $0.00282 |
| Sonnet 5.5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
code-standards 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.
The source is not reproduced here
Licensed MIT-0
The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 64 lines · 0 tokens per session scan A 0973d5eb100e
code-standards is a skill published in the GitHub repository aws-samples/serverless-samples (351 stars, last pushed 2d ago), licensed MIT-0. It costs nothing until one of its globs matches a file; then it loads 704 tokens. 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
serverless-expert
Design and implement production-grade serverless applications with optimal performance, cost efficiency, and scalability. Use when the user mentions serverless or FaaS, AWS Lambda, Azure Functions, Cloud Functions, cold starts, event-driven architecture, or API Gateway-fronted workloads.
performing-serverless-function-security-review
Performing security reviews of serverless functions across AWS Lambda, Azure Functions, and GCP Cloud Functions to identify overly permissive execution roles, insecure environment variables, injection vulnerabilities, and missing runtime protections.
cis-aws-compute-12.8
Ensure that Code Signing is enabled for Lambda functions.
cis-aws-compute-12.10
Ensure Lambda functions do not allow unknown cross account access via permission policies.
cis-aws-compute-12.11
Ensure that the runtime environment versions used for your Lambda functions do not have end of support dates.
cis-aws-compute-12.12
Ensure encryption in transit is enabled for Lambda environment variables.