Borrowing it
Nothing to install: this file belongs to lgallard/terraform-aws-backup. 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/lgallard/terraform-aws-backup/master/CLAUDE.mdgit clone --depth 1 https://github.com/lgallard/terraform-aws-backupWrote 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/lgallard/terraform-aws-backup/claude-md)<a href="https://agentmods.dev/instructions/lgallard/terraform-aws-backup/claude-md"><img src="https://agentmods.dev/badge/instructions/lgallard/terraform-aws-backup/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.04533 | $0.04533 |
| Opus 5 | $0.02266 | $0.02266 |
| Sonnet 5 | $0.00907 | $0.00907 |
| Haiku 4.5 | $0.00453 | $0.00453 |
Grade A, and why
terraform-aws-backup 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 6d 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 — 615 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform AWS Backup Module - Development Guidelines
Overview
This document outlines Terraform-specific development guidelines for the terraform-aws-backup module, focusing on best practices for AWS infrastructure as code.
Module Structure & Organization
File Organization
- main.tf - Primary resource definitions and locals
- variables.tf - Input variable definitions with validation
- outputs.tf - Output value definitions
- versions.tf - Provider version constraints
- iam.tf - IAM roles and policies
- notifications.tf - SNS and notification configurations
- organizations.tf - AWS Organizations backup policies
- selection.tf - Resource selection logic
- reports.tf - Backup reporting configurations
- audit_manager.tf - Audit framework configurations
Code Organization Principles
- Group related resources logically in separate files
- Use descriptive locals for complex expressions
- Maintain backward compatibility with existing variable names
- Keep validation logic close to variable definitions
MCP-Powered Validation Workflow
Development Lifecycle with MCP Integration
Before Implementation:
# Validate resource documentation
Terraform MCP: "Look up aws_backup_vault resource documentation"
Context7: "Get AWS Backup best practices"
During Development:
# Validate syntax and arguments
Terraform MCP: "Validate aws_backup_plan arguments"
Terraform MCP: "Check aws_backup_selection resource requirements"
Validation Phase:
# AI-powered validation
Task Agent (general-purpose): "Validate implementation comprehensively"
Task Agent (Explore - thorough): "Analyze code patterns and dependencies"
Security Review:
# Validate security configurations
Context7: "AWS Backup encryption best practices"
Terraform MCP: "Look up aws_kms_key for backup vault"
Terraform Best Practices
Resource Creation Patterns
Favor for_each over count for resource creation:
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.
- 6d ago First seen · 615 lines · 4,533 tokens per session scan A b5cd864127aa
terraform-aws-backup CLAUDE.md is an instructions file published in the GitHub repository lgallard/terraform-aws-backup (159 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,533 tokens to every session, about $0.0227 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.