Borrowing it
Nothing to install: this file belongs to robinmordasiewicz/terraform-provider-f5xc. 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/robinmordasiewicz/terraform-provider-f5xc/main/.claude/skills/terraform-registry-inspector/SKILL.mdgit clone --depth 1 https://github.com/robinmordasiewicz/terraform-provider-f5xcWrote 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/robinmordasiewicz/terraform-provider-f5xc/terraform-registry-inspector)<a href="https://agentmods.dev/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-registry-inspector"><img src="https://agentmods.dev/badge/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-registry-inspector/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-registry-inspector"><img src="https://agentmods.dev/badge/skills/robinmordasiewicz/terraform-provider-f5xc/terraform-registry-inspector.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.04851 |
| Opus 5 | $0.00036 | $0.02426 |
| Sonnet 5 | $0.00014 | $0.00970 |
| Haiku 4.5 | $0.00007 | $0.00485 |
Grade A, and why
terraform-registry-inspector 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 12d 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 — 766 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Registry Documentation Inspector
A specialized skill for investigating Terraform provider documentation rendering on the Terraform Registry using Chrome DevTools MCP server capabilities.
Purpose
This skill enables systematic investigation of:
- Provider documentation rendering quality
- Version availability and selection
- Resource/data-source documentation navigation
- Subcategory organization
- Source code repository links
- Markdown rendering issues
Gold Standard Reference: Azure RM Provider
The HashiCorp Azure RM Provider (hashicorp/azurerm) represents the gold standard for professional Terraform provider documentation. All quality assessments should be benchmarked against this reference.
Gold Standard URL: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs
Gold Standard Quality Elements
Provider Index Page Excellence
| Element | Azure RM Implementation |
|---|---|
| Provider Description | Links to official Microsoft Azure documentation |
| Clear Sections | Data Sources explanation, Resources explanation |
| External Links | Tutorial links, changelog reference |
| Authentication | Multiple auth method guides as separate linked pages |
| Note Callouts | Important warnings with proper formatting |
| Issue Reporting | "Bugs and Feature Requests" section with GitHub links |
Subcategory Organization (100+ Subcategories)
Azure RM organizes resources by Azure service domain:
- AAD B2C, API Management, Active Directory Domain Services
- App Configuration, App Service (Web Apps), Application Insights
- Compute, Container, Container Apps, CosmosDB
- Database, DNS, Key Vault, Load Balancer
- Machine Learning, Monitor, Network, Storage
- And 80+ more service-specific categories
Best Practice: Group resources by service/domain, not alphabetically.
Dedicated Sections
| Section | Purpose |
|---|---|
| Guides | Authentication guides, migration guides, best practices |
| Functions | Provider-defined functions with clear signatures |
| Resources | Organized by subcategory with clear naming |
| Data Sources | Mirror resource organization patterns |
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.
- 12d ago First seen · 766 lines · 71 tokens per session scan A 39a92135b78f
terraform-registry-inspector is a skill published in the GitHub repository robinmordasiewicz/terraform-provider-f5xc (2 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 4,851 once invoked, about $0.0004 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
protected-vercel-deployments
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection with agent-browser. Use when a preview or production URL redirects to a Vercel login page, returns a protection 401 or 403, or needs short-lived Trusted Sources OIDC authentication instead of a static bypass secret or…
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across…
agentcore
Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS"…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
lovable
Lovable MCP tool usage — deploy projects, message agent, test with agent-browser. Minimize credits by delegating to local repo.
agent-browser
Browser automation via Chrome/Chromium CDP — open, snapshot, click, screenshot. For testing web apps, mobile layouts, and automated interactions without Playwright/Puppeteer.