Agent skill

Provider Verification

by mondoohq in mondoohq/mql

Verify mql provider resource/field changes against real cloud infrastructure.

Custom licenceAuto-check passedDevOps & Cloud

Install Provider Verification

skills CLI
$ npx skills add mondoohq/mql --skill provider-verification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mondoohq/mql provider-verification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mondoohq/mql.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/provider-verification .claude/skills/provider-verification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
provider-verification
GitHub stars
412
Token cost
~3.7k tokens
SKILL.md length
1,743 words
Files
3 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Custom licence

At a glance

Verify mql provider resource/field changes against real cloud infrastructure.

  • Works in 12 steps: Extract what changed → Build the affected providers → Check cloud auth → …
  • It even when the user only says test this PR in the context of an mql provider change
  • SKILL.md covers Inputs, Workflow, Key rules and Reference
  • Runs Python scripts from its folder; calls terraform, aws and python3

What it does

Provider Verification is an agent skill from mondoohq/mql. Verify mql provider resource/field changes against real cloud infrastructure. Given a pull request or a commit range, this provisions Terraform infra in the affected cloud(s), runs mql queries against every new or changed resource and field, reports the hourly cost (pausing for approval above $2/hr), opens a fix PR for any provider bugs it uncovers, and tears the infrastructure back down. Use this whenever someone wants to test, verify, smoke-test, or "prove out" a provider PR or a range of commits against live…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `extract_changes.py` and `references/cloud-notes.md`).

It sits in DevOps & Cloud, covering Infrastructure as code, QA and bug reports and Pull requests. It works with Google Cloud, Terraform, Microsoft Azure and Amazon Web Services. The repository describes itself as: open source, cloud-native, graph-based query language.

When your agent uses it

  • It even when the user only says test this PR in the context of an mql provider change
  • Tasks that involve Infrastructure as code
  • Tasks that involve QA and bug reports

Example prompts

  • “prove out”
  • “verify PR 7701 works”
  • “spin up infra to test the new GCP resources”
  • “/provider-verification”

Requirements

  • Python 3

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Extract what changed
  2. Build the affected providers
  3. Check cloud auth
  4. Pre-flight: remove leftovers from prior runs
  5. Generate Terraform
  6. Cost gate
  7. Apply
  8. Verify with mql run
  9. Triage bugs
  10. Fix PR
  11. Teardown — always
  12. Report

What it can do on your machine

Read from SKILL.md and the folder at commit ffbaa58. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • terraform
    • aws
    • python3
    • make
    • az
    • gh
    • gcloud
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use aws, az, gh, gcloud and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Provider Verification loads about 3.7k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 207 tokens; SKILL.md has 1,743 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~207
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,743 words (~3,669 tokens).

“mql resources are thin wrappers over cloud APIs, so a .lr schema change is only really "done" once it has been run against a real cloud account. This skill automates that loop: figure out what changed, stand up just enough…”

— opening of SKILL.md by mondoohq, Custom licence
name
provider-verification

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in .agents/skills/provider-verification of mondoohq/mql.

  • SKILL.md
  • extract_changes.py
  • references/cloud-notes.md

Open the folder on GitHubat commit ffbaa58

Compare with similar skills

Provider Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Provider Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Provider Verification this skillmondoohq/mql412—~3.7kAutomated safety check: PassCustom licence
Terravision Cloud Diagramspatrickchugh/terravision1.6k—~5.6kAutomated safety check: NotesAGPL-3.0-only
TerrasharkLukasNiessen/terrashark716—~843Automated safety check: PassMIT
Terraform Module Librarywshobson/agents40k11 repos~1.3kAutomated safety check: PassMIT
Atmos Migrationcloudposse/atmos1.4k—~5.1kAutomated safety check: WarnApache-2.0
Tsh Implementing Terraform ModulesTheSoftwareHouse/copilot-collections284—~1.6kAutomated safety check: PassMIT

Similar skills

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated 3 days ago
    DevOps & CloudAuto-check: notes
  • Terrashark

    LukasNiessen/terrashark

    Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps.

    716 GitHub stars~843 tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed
  • Build reusable, tested Terraform modules for AWS, Azure, GCP and OCI, with a standard file layout, an AWS VPC example, versioning rules and Terratest checks.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    DevOps & CloudAuto-check passed
  • Atmos Migration

    cloudposse/atmos

    Migrate to Atmos from native Terraform, Terraform Workspaces, Terramate, Terragrunt, Make, Just, or Task; migrate tool versions from mise or Aqua CLI; migrate AWS/GCP/Azure CLI configs, Leapp…

    1.4k GitHub stars~5.1k tokensUpdated today
    DevOps & CloudAuto-check: warnings
  • Tsh Implementing Terraform Modules

    TheSoftwareHouse/copilot-collections

    Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices.

    284 GitHub stars~1.6k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • Cloud Architect

    davila7/claude-code-templates

    Expert cloud architect specializing in AWS/Azure/GCP multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns.

    33k GitHub starsUsed in 8 repos~1.9k tokens
    DevOps & CloudAuto-check passed

More from mondoohq/mql

All 9 skills in this repo
  • Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

    412 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Upgrade an mql provider's vendored SDKs (all providers or a named subset), audit the new versions for breaking changes and fix call sites while keeping shipped MQL fields backwards-compatible, check…

    412 GitHub stars~4.5k tokensUpdated today
    Auto-check passed
  • New Provider

    mondoohq/mql

    Scaffold a new mql provider. An agent skill from mondoohq/mql.

    412 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • New Resource

    mondoohq/mql

    Add or change a resource in an existing mql provider — schema, codegen, implementation, tests, and verification against a real target.

    412 GitHub stars~5.6k tokensUpdated today
    Auto-check passed
  • Provider Release

    mondoohq/mql

    Release mql providers and cut mql/cnspec releases, stable or pre-release.

    412 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Staged Discovery

    mondoohq/mql

    Add staged discovery support to a provider. An agent skill from mondoohq/mql.

    412 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Questions about Provider Verification

What does Provider Verification do?

Verify mql provider resource/field changes against real cloud infrastructure. Provider Verification is an agent skill from mondoohq/mql. Verify mql provider resource/field changes against real cloud infrastructure.

When should I use Provider Verification?

Provider Verification fits situations like: it even when the user only says test this PR in the context of an mql provider change; tasks that involve Infrastructure as code; tasks that involve QA and bug reports.

How do I install Provider Verification in Claude Code?

Run `npx skills add mondoohq/mql --skill provider-verification -a claude-code`. Or copy the skill folder (.agents/skills/provider-verification in mondoohq/mql) into .claude/skills/provider-verification in your project. Claude Code loads it when a task matches its description.

How do I install Provider Verification in Codex?

Run `npx skills add mondoohq/mql --skill provider-verification -a codex`. Or copy the skill folder (.agents/skills/provider-verification in mondoohq/mql) into .agents/skills/provider-verification in your project. Codex loads it when a task matches its description.

Can I use Provider Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mondoohq/mql --skill provider-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/provider-verification, .gemini/skills/provider-verification, .github/skills/provider-verification and .opencode/skills/provider-verification in your project.

What does Provider Verification need to run?

Going by SKILL.md and its folder, Provider Verification needs Python for the scripts in its folder and the command-line tools its instructions call (terraform, aws, python3, make, az and gh). Our summary lists: Python 3.

Does Provider Verification access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Provider Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Provider Verification use?

Provider Verification has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Provider Verification use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Provider Verification?

Skills that share tags, products or a category with Provider Verification: Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars), Terrashark (LukasNiessen/terrashark, 716 stars), Terraform Module Library (wshobson/agents, 40k stars) and Atmos Migration (cloudposse/atmos, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Provider Verification?

mondoohq (a GitHub organization) maintains it in mondoohq/mql, which has 412 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.

Source: mondoohq/mql on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.