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 skills/infraspecdev/tesseract/terraform-test-coveragenpx skills add infraspecdev/tesseract --skill terraform-test-coveragegit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/terraform-test-coverage)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/terraform-test-coverage"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/terraform-test-coverage.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.00035 | $0.00866 |
| Opus 5 | $0.00017 | $0.00433 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
terraform-test-coverage 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- terraform-test-coverage — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Test Coverage Assessment
Overview
Test quality assessment for Terraform components using the native terraform test framework (.tftest.hcl files). Evaluates coverage across 6 dimensions and provides patterns for mock_provider, override_resource, and plan-only assertions.
When to Use
- Reviewing existing
.tftest.hclfiles for coverage gaps - Designing new tests for a Terraform component
- After adding new variables, resources, or feature flags
- Assessing whether a component is adequately tested before release
When NOT to Use
- For non-native test frameworks (Terratest, kitchen-terraform)
- For syntax or formatting checks -- use
terraform validate/terraform fmt - For security auditing -- use the
terraform-security-auditskill - For module API design or variable naming reviews
- When the component has no
.tftest.hclfiles and you are not asked to create them
Coverage Dimensions
Assess each component against these 6 dimensions (see test-patterns.md for HCL examples):
- Happy Path --
runblock withcommand = plan, valid inputs, assertions on key resource attributes - Variable Validation -- Every
validationblock has a test usingexpect_failures - Feature Toggles -- Every enable/disable flag tested in both states
- Edge Cases -- Boundary values, empty collections, single-AZ, all features disabled
- CIDR Math -- Subnet CIDRs do not overlap, fit within VPC CIDR, correct AZ distribution (N/A for non-networking)
- Naming Conventions -- Name tags and environment/stage propagate consistently
Workflow
- Discover tests: Find all
.tftest.hclfiles in the component - Inventory variables: Read
variables.tfto list all required variables, validation blocks, and feature toggle flags - Map coverage: For each
runblock, determine which dimension(s) it covers - Identify gaps: Cross-reference dimensions against existing tests. Flag missing coverage
- Assess quality: Check assertion depth -- tests should verify specific attributes, not just "plan succeeds"
- Produce report: Use the template from
templates.md
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 70 lines · 35 tokens per session scan A 290c7e28dd11
terraform-test-coverage is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 866 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…