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 instructions/ran-isenberg/aws-lambda-handler-cookbook/claude-mdgit clone --depth 1 https://github.com/ran-isenberg/aws-lambda-handler-cookbookWrote 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/ran-isenberg/aws-lambda-handler-cookbook/claude-md)<a href="https://agentmods.dev/instructions/ran-isenberg/aws-lambda-handler-cookbook/claude-md"><img src="https://agentmods.dev/badge/instructions/ran-isenberg/aws-lambda-handler-cookbook/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 | $0.00643 | $0.00643 |
| Opus 5 | $0.00321 | $0.00321 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
aws-lambda-handler-cookbook 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 5d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code in this repository. Topic rules live in .claude/rules/ and load automatically (path-scoped ones only when you touch matching files).
Project
Production-grade blueprint for AWS Serverless services in Python: a Lambda handler skeleton plus CDK deployment code, a CI/CD pipeline, and tests.
- Runtime: Python
>=3.14, managed withuv. Infra: AWS CDK. Docs: MkDocs → GitHub Pages.
Layout
- service/ — app code, layered
handlers/→logic/→dal/, withmodels/(Pydantic) shared. - cdk/ — CDK stacks and constructs (
cdk/service/). - tests/ —
unit/,integration/,infrastructure/,e2e/. - docs/ — documentation and runnable examples.
Rules index
.claude/rules/makefile.md— command reference; always usemaketargets. (loaded every session).claude/rules/github-actions.md— CI workflows; SHA-pinning. (scoped to.github/workflows/).claude/rules/service.md— handler/logic/dal layering, Powertools, Pydantic. (scoped toservice/).claude/rules/models.md— Pydantic model conventions and placement. (scoped toservice/**/models/).claude/rules/testing.md— unit / integration / e2e / infra test patterns. (scoped totests/).claude/rules/cdk.md— construct and stack structure. (scoped tocdk/).claude/rules/docs.md— Zensical build, markdownlint, OpenAPI sync. (scoped todocs/).claude/rules/security.md— secrets, IAM, cdk-nag, WAF, OIDC. (loaded every session).claude/rules/dependencies.md— uv + npm,make update-deps, audits. (loaded every session).claude/rules/git-pr.md— Conventional Commits, release bumps, PR labels. (loaded every session)
Planning (plan mode)
- Explore the relevant
service/layer and its tests before proposing changes; name the files you'll touch. - Respect the layering — never move logic into handlers or bypass the DAL.
- Every behavior change names the suite that covers it and updates/adds tests.
- Never run cloud-mutating commands while planning or exploring —
make deploy/destroy,cdk deploy/destroy,aws …. Planning uses read-only and local commands only. - Verify before claiming done: run
make lintplus the narrowest relevant suite; report real output.
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.
- 5d ago First seen · 41 lines · 643 tokens per session scan A bbb7b42ca42e
aws-lambda-handler-cookbook CLAUDE.md is an instructions file published in the GitHub repository ran-isenberg/aws-lambda-handler-cookbook (680 stars, last pushed 26d ago), licensed MIT. It adds 643 tokens to every session, about $0.0032 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
Baton CLAUDE.md
Instructions for zhu-xiaowei/Baton, covering baton — project context, workflow rules, what is this, core design principle and current status.
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
workflow AGENTS.md
AGENTS.md instructions for vercel/workflow, covering agent instructions, architecture, core components, workflow execution model and development commands.
cookiecutter-mlops-package AGENTS.md
Instructions for fmind/cookiecutter-mlops-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.
microfeed AGENTS.md
AGENTS.md instructions for microfeed/microfeed, covering repository guidance, development workflow, instance management and cloudflare deployment, source architecture and theme repositories.
aws-bench AGENTS.md
AGENTS.md instructions for aws-bench/aws-bench, covering agents.md, setup, commands, project structure and code style.