ClawHub
Back to skill

Security audit

ctyun-analyze-billing

Security checks for vulnerabilities and agentic risk

Overview

This skill is a constrained CTYUN billing-analysis helper that uses read-only CLI queries and includes clear privacy and credential safeguards.

Install only if you use CTYUN billing data and are comfortable letting the agent run read-only ctyun-cli billing queries through your already configured local account. Do not share AccessKey or SecretKey with the agent, and review outputs for proper masking of account, order, transaction, and resource identifiers.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Scope Creep

Low
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.

Content

Scanner excerpt · SKILL.md (reported line 37)May include surrounding context.

md
1. Set the billing period or date range, filters, question, and money basis. Keep the original field name when `amount`, `payableAmount`, or `price` is unclear.
2. Read [bill Actions](references/bill-actions.md) and [query catalog](references/query-catalog.md). Choose the smallest `bill` query that can answer the question. For an Action not in the list, run `ctyun-cli bill --help` and `ctyun-cli bill <Action> --help`. Check that it is read-only and confirm its scope, flags, pagination, and response fields.
3. Read [evidence policy](references/evidence-policy.md). Use P1 only when the bill does not explain a charge, the user asks for a check, or there is a dispute. Limit each resource query with a bill-derived `resourceId`, region, project, order, or time. Use P2 only when P0/P1 is not enough or the user asks.
4. Check whether all pages were returned. If not, do not claim a full check. If bill and resource data disagree, the bill API is the source of truth. Stop when the question is answered, no useful query remains, an ID is missing, or the next query would expand the scope.
5. Read [dialogue report specification](references/report-spec.md). Show only the needed redacted result. Label each important amount or conclusion as `Direct bill API value`, `Checked calculation`, `Partial data`, or `Cannot determine`.

## Reference navigation