v1.0.0

Finops Cloud Optimizer

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 4:40 AM.

Analysis

This skill appears purpose-aligned for cloud cost analysis, but it needs careful review because it can use logged-in cloud accounts to read sensitive billing and resource information across broad scopes.

GuidanceUse this only with read-only, least-privilege cloud credentials and an explicit account/project/subscription scope. Review the CLI commands before running them, protect any exported billing files, and require separate human approval for any real cloud purchasing or commitment decisions such as reserved instances or Savings Plans.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

SKILL.md

Pull billing data and break it down by service, account, and tag: ... --group-by Type=DIMENSION,Key=LINKED_ACCOUNT ... --group-by Type=TAG,Key=Environment Type=TAG,Key=Team

The skill uses raw cloud CLI/API commands to enumerate account and tag-based billing data. This is purpose-aligned, but it should be scoped carefully before use.

User impactThe agent may gather more cloud account and tag detail than intended if the active CLI context is broad.

RecommendationReview commands before running them, set explicit scope, and prefer exported billing files when live cloud API access is not necessary.

Agentic Supply Chain Vulnerabilities

SeverityInfoConfidenceHighStatusNote

Requirements

Required binaries (all must exist): none ... Required env vars: none ... Primary credential: none

The skill is instruction-only, but its documented workflow depends on external cloud CLIs and authenticated environments that are not declared in the registry requirements.

User impactUsers may not realize from the registry metadata that the skill expects preconfigured cloud CLI tools and credentials.

RecommendationConfirm the installed CLIs are trusted, up to date, and pointed at the intended cloud accounts before invoking the skill.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityMediumConfidenceHighStatusConcern

SKILL.md

The agent needs access to billing data and resource metrics. At least one of: ... aws ce get-cost-and-usage ... gcloud billing accounts list ... az consumption usage list ... Scope — specific account/project/subscription, or all

These commands rely on authenticated cloud identities and may run against broad cloud scopes, while the supplied requirements list no primary credential or explicit permission boundary.

User impactIf run with broad default cloud credentials, the agent could read billing and resource information across many accounts, projects, or subscriptions.

RecommendationUse a least-privilege, read-only FinOps/billing role; specify exact profiles, projects, subscriptions, and accounts; avoid running with admin or organization-wide defaults unless intentionally approved.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Memory and Context Poisoning

SeverityLowConfidenceHighStatusNote

SKILL.md

--output json > /tmp/aws-costs-by-service.json ... > /tmp/aws-costs-by-account.json ... --output json > /tmp/azure-usage.json

The examples write cloud billing and account data into local temporary files, with no cleanup or retention guidance.

User impactSensitive cost, account, and tag data may remain on disk after the analysis.

RecommendationStore exports in a protected location, avoid including sensitive tag values where possible, and delete temporary billing files after use.