Antigravity Quota 1.1.0
Analysis
The quota checker appears purpose-aligned, but it reads local Clawdbot auth profiles and uses stored refresh tokens for all Antigravity accounts while the registry metadata does not declare that credential access.
Findings (3)
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.
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.
Primary credential: none; Required config paths: none
The registry metadata under-states the operational requirement because the included script exits unless it can read Clawdbot auth profile files containing Antigravity account credentials.
go install github.com/joargp/tablesnap/cmd/tablesnap@latest
The optional image-output workflow asks users to install a third-party tool at the moving @latest version, which is an unpinned dependency.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
profiles = JSON.parse(fs.readFileSync(profilesPath, 'utf-8')); ... refresh: value.refresh ... refresh_token: refreshTokenValue
The code reads local Clawdbot auth profiles, extracts stored refresh tokens for google-antigravity accounts, and uses those tokens to obtain access tokens. That is high-impact credential/session access even though it is coherent with quota checking.
