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 darellchua2/opencode-config-template --skill opentofu-aws-explorer-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/opentofu-aws-explorer-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/opentofu-aws-explorer-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/opentofu-aws-explorer-skill.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.00024 | $0.07557 |
| Opus 5 | $0.00012 | $0.03778 |
| Sonnet 5 | $0.00005 | $0.01511 |
| Haiku 4.5 | $0.00002 | $0.00756 |
Grade C, and why
opentofu-aws-explorer-skill scanned grade C with 2 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 4d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
# ~/.aws/credentials with profiles Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://registry.terraform.io/ How it starts
The opening of the file, as written. The whole thing — 1,199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTofu AWS Explorer
What I do
I guide you through managing Amazon Web Services (AWS) infrastructure using the AWS provider for OpenTofu/Terraform. I help you:
- Compute Resources: Manage EC2, Lambda, ECS, and container resources
- Networking: Create VPCs, subnets, route tables, and security groups
- Storage: Configure S3, EBS, EFS, and file systems
- Databases: Setup RDS, DynamoDB, ElastiCache, and Redshift
- Security: Implement IAM, KMS, Security Groups, and WAF
- Best Practices: Follow AWS Well-Architected Framework and provider documentation
When to use me
Use this skill when you need to:
- Provision AWS infrastructure as code
- Automate AWS resource creation and management
- Implement multi-tier architectures (web, app, data)
- Setup secure networking and VPC configurations
- Manage IAM roles, policies, and security groups
- Configure AWS services for production workloads
- Implement AWS best practices and governance
Note: OpenTofu and Terraform are used interchangeably throughout this skill. OpenTofu is an open-source implementation of Terraform and maintains full compatibility with Terraform providers.
Prerequisites
- OpenTofu CLI installed: Install from https://opentofu.org/docs/intro/install/
- AWS Account: Valid AWS account with appropriate permissions
- AWS Credentials: Access keys or IAM role for authentication
- Basic AWS Knowledge: Understanding of AWS services and concepts
Provider Setup: Complete the opentofu-provider-setup skill first for provider authentication and state backend configuration. This skill focuses on AWS resource management, not provider setup.
Provider Documentation
- Terraform Registry (AWS Provider): https://registry.terraform.io/providers/hashicorp/aws/latest/docs
- Latest Provider Version: hashicorp/aws ~> 5.0.0
- Provider Source: https://github.com/hashicorp/terraform-provider-aws
- AWS Well-Architected Framework: https://docs.aws.amazon.com/wellarchitected/
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.
- 4d ago First seen · 1,199 lines · 24 tokens per session scan C c24a843f4b52
opentofu-aws-explorer-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 7,557 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
terraform-best-practices
Terraform and Infrastructure as Code optimization guidelines from Terramate. This skill should be used when writing, reviewing, or refactoring Terraform/OpenTofu code to ensure optimal patterns for security, maintainability, and reliability. Triggers on tasks involving Terraform modules, infrastructure provisioning…
terramate-best-practices
Terramate CLI, Cloud, and Catalyst best practices and usage guides. This skill should be used when working with Terramate stacks, orchestration, code generation, Cloud integration, or Catalyst components and bundles.
terraform-iac
Terraform and OpenTofu infrastructure as code best practices - generate HCL configurations, module patterns, state management, CI/CD workflows, and cloud provider templates for AWS, GCP, Azure.
tf-plan-review
Analyze Terraform plans for risk before you apply. Classifies every change as safe, moderate, dangerous, or critical. Detects destroys, IAM changes, data-loss risks, and blast radius. Entirely read-only — never runs apply.
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).