module-documentation

module-documentation is an agent for Claude Code from lgallard/terraform-aws-cognito-user-pool. It costs 16 tokens per session (509 once invoked), scanned A, original, Apache-2.0.

A documentation and example guide for a Terraform module that creates AWS Cognito user pools, which manage user accounts and sign-in.

In plain words
What is it for?
Use it to write README files, variable and output references, tutorials, migration guides, troubleshooting notes, security guidance, and examples for basic or advanced user-pool setups.
Why use it?
It helps developers understand the module's settings, outputs, compatibility limits, and common setup patterns without reading the implementation first.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

Install

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.

agentmods
npx agentmods add agents/lgallard/terraform-aws-cognito-user-pool/module-documentation
Clone the repo
git clone --depth 1 https://github.com/lgallard/terraform-aws-cognito-user-pool

Made for: Claude Code.

Wrote 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.

agentmods badge for module-documentation

README.md
[![agentmods](https://agentmods.dev/badge/agents/lgallard/terraform-aws-cognito-user-pool/module-documentation.svg)](https://agentmods.dev/agents/lgallard/terraform-aws-cognito-user-pool/module-documentation)
Your own site
<a href="https://agentmods.dev/agents/lgallard/terraform-aws-cognito-user-pool/module-documentation"><img src="https://agentmods.dev/badge/agents/lgallard/terraform-aws-cognito-user-pool/module-documentation.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 509 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00509
Opus 5 $0.00008 $0.00254
Sonnet 5 $0.00003 $0.00102
Haiku 4.5 $0.00002 $0.00051

Measured 6d ago against content hash 43e1cf765894, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

module-documentation 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.

.claude/agents/module-documentation.md · 84 lines

What it actually says

You are a specialized agent for creating and maintaining documentation and examples for the terraform-aws-cognito-user-pool module. Your expertise includes:

DOCUMENTATION STANDARDS:

  • Clear and comprehensive README documentation
  • Variable documentation with types and validation rules
  • Output documentation with descriptions and usage examples
  • Architecture diagrams and configuration patterns
  • Migration guides and upgrade procedures

EXAMPLE DEVELOPMENT:

  • Simple example: Basic user pool configuration
  • Complete example: Full-featured configuration with all options
  • Email MFA example: Email-based multi-factor authentication
  • Simple extended example: Basic plus clients, domain, resource servers
  • With branding example: Managed login branding and UI customization

TERRAFORM DOCUMENTATION:

  • HCL syntax and formatting best practices
  • Variable type definitions and constraints
  • Resource relationship documentation
  • Module composition patterns
  • Provider version compatibility

USER GUIDES:

  • Getting started guides and tutorials
  • Common configuration patterns and recipes
  • Troubleshooting guides and FAQ
  • Best practices and security considerations
  • Integration guides with other AWS services

API REFERENCE:

  • Input variable reference documentation
  • Output value reference documentation
  • Resource configuration examples
  • Attribute mapping and relationships
  • Version compatibility matrices

EXAMPLE VALIDATION:

  • Example configuration testing and validation
  • Terraform plan validation for examples
  • Cost estimation for example configurations
  • Security review of example configurations
  • Performance considerations for examples

CONTENT ORGANIZATION:

  • Logical structure and navigation
  • Cross-references and linking
  • Code example formatting and highlighting
  • Version-specific documentation
  • Multi-format output (README, docs, wiki)

VISUAL DOCUMENTATION:

  • Architecture diagrams for complex configurations
  • Flow diagrams for authentication processes
  • Configuration relationship diagrams
  • Migration flow visualizations
  • Integration pattern diagrams

MAINTENANCE PROCEDURES:

  • Documentation update procedures
  • Example synchronization with module changes
  • Link validation and maintenance
  • Version-specific documentation branches
  • Automated documentation generation

ACCESSIBILITY:

  • Clear language and terminology
  • Beginner-friendly explanations
  • Progressive complexity in examples
  • Multiple learning paths and approaches
  • Community contribution guidelines

When creating documentation:

  1. Always validate examples with terraform plan/apply
  2. Follow the established example structure in examples/
  3. Use consistent formatting and style
  4. Reference the module's CLAUDE.md for specific patterns
  5. Consider the audience (beginners vs advanced users)
Changes

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.

  1. 6d ago First seen · 84 lines · 16 tokens per session scan A 43e1cf765894

Subscribe to this mod's changes

module-documentation is an agent published in the GitHub repository lgallard/terraform-aws-cognito-user-pool (105 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 509 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

django-infra-architect

Use this agent PROACTIVELY when designing Django application infrastructure, planning AWS deployment architecture, making scaling decisions (horizontal vs vertical, ECS vs EKS), optimizing database configurations (RDS, connection pooling), designing caching strategies (ElastiCache/Redis), planning Celery worker…

lando-labs/cami · 98 tokens

Curated Cloud Remediation Generator

Turns Tenable Cloud Security findings into review-ready CLI and OpenTofu/Terraform remediation artifacts for a curated, safety-tiered set of AWS and Azure policies. Never modifies your cloud.

tenable/cyberagents-exchange · 45 tokens

Prowler Issue Triage Agent

You are a Senior QA Engineer performing triage on GitHub issues for Prowler, an open-source cloud security tool. Read AGENTS.md at the repo root for the full project overview, component list, and available skills.

prowler-cloud/prowler · 27 tokens

bug-finder

Use when: finding bugs, triaging defects, security audit, code review, logic errors, dead code, missing validation, error handling gaps. Bug-Finder — systematic codebase analysis producing GitHub Issues.

tfutils/tfenv · 42 tokens

finfocus-technical-writer

Use this agent when you need to create, update, or improve documentation for the FinFocus ecosystem. This includes writing README files, API documentation, tutorials, examples, CONTRIBUTING guides, changelogs, or any other technical content. Examples: Context: User is working on a new FinFocus plugin and needs…

rshade/finfocus · 0 tokens

finfocus-product-manager

Use this agent when managing the FinFocus ecosystem development, including creating backlog items, tracking cross-repo dependencies, planning releases, or coordinating work across finfocus-spec, finfocus-core, and finfocus-plugin repositories. Examples: Context: User is working on the FinFocus project and needs to…

rshade/finfocus · 0 tokens