A read-only skill for investigating a project's cloud security posture through the Wiz security service. It routes questions to the correct security area and examines the project's own resources.

Use it to inspect issues in areas such as source-code security and container security through Wiz. It requires the Wiz connection to be enabled and the project's resource identifiers to be configured.

It gives an agent a defined investigation process and prevents accidental changes while reviewing cloud-security findings.

How AlexisBalayre/claude-code-power-config configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/skills/wiz/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-config

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/wiz/github.svg)](https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/wiz)

Your own site

<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/wiz"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/wiz/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/wiz"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/wiz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,533 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.01533
Opus 5	$0.00016	$0.00766
Sonnet 5	$0.00007	$0.00307
Haiku 4.5	$0.00003	$0.00153

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

Security

Grade A, and why

wiz 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 10d 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/skills/wiz/SKILL.md · 70 lines

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.

Wiz (cloud security)

The Wiz MCP exposes ~250 tools across 24 security domains behind two gateway tools. You never call a Wiz tool directly: discover finds it, execute runs it. This skill is read-only: investigate, never mutate.

Setup: this skill needs the Wiz MCP server enabled in .claude/settings.local.json and your own Wiz resource IDs in .env (see .env.example): WIZ_REPO_BRANCH_ID (the default-branch REPOSITORY_BRANCH resource for SAST) and WIZ_CONTAINER_REPO_IDS (the container-repository UUIDs for your images). Resolve them once per the "Resolve to IDs" section below, then fill them in — never hardcode real UUIDs in the repo.

The loop

Every query takes the same four steps:

Route. Call discover() with no argument to list the domains. Pick the one domain that owns the answer by the type of finding you want, not by nouns in the question (see Routing traps).
Spec. Call discover(domain) for the exact tool name and its parameter schema. Read it: params that sound singular are usually arrays (group_by, severity, status, asset_name, container_repository), some are required (e.g. list_issues_grouped needs group_by + type), and the first / limit cap differs per tool (often 20). Never guess.
Query. Call execute(tool_name, parameters) with the exact name from step 2, scoped per the project section below. If execute rejects the name, re-run discover(domain) to confirm spelling (some names repeat across domains).
Summarize. A result too large for one response is auto-saved to a tool-results/*.txt file instead of returned. Parse it with jq or python (or hand the file to a subagent), never re-read it whole. Report a ranked summary (severity, then affected resource) with the Wiz finding IDs so the user can open each in the portal. Never paste raw JSON back.

Prefer a *_grouped tool with a small first over a raw list: fewer tokens, and it answers "where is the load" directly.

Read the full file on GitHub · 70 lines

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.

10d ago First seen · 70 lines · 33 tokens per session scan A a45b6482d256

Subscribe to this mod's changes

wiz is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,533 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.

Claude Code Cloud DevOps and cloud Security agents ai anthropic claude developer-tools

monitoring-alerting

Monitoring and alerting design reviewer for production backend services. ALWAYS use when writing Prometheus alerting rules, designing Grafana dashboards, defining SLI/SLO, configuring alert routing (PagerDuty/OpsGenie/Slack), or reviewing existing monitoring setups. Covers SLI/SLO definition, alert rule quality…

johnqtcg/awesome-skills · 137 tokens

cost-optimization

Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.

wshobson/agents · 48 tokens

hybrid-cloud-networking

Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.

wshobson/agents · 47 tokens

claude-code-power-config: Skill for Claude Code