Back to skill

Security audit

Context Usage Checker

Security checks for vulnerabilities and agentic risk

Overview

This skill only estimates current conversation token usage and replies with an aggregate status message, with no evidence of exfiltration, persistence, or destructive behavior.

Before installing, be aware that the skill can read the current conversation history while calculating token usage, although it only reports aggregate counts. It also appears intended for Chinese-language use and may trigger from broad token/context usage phrases.

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
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (10)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill advertises activation through broad natural-language phrases such as asking to check context or token usage, without defining strict invocation boundaries. This can cause accidental triggering during ordinary conversation, leading the agent to expose session metadata or change behavior unexpectedly when the user did not intend to invoke the skill.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The manifest description is written entirely in Chinese and provides no indication that the skill supports other languages or lets the user choose a locale. Under the policy for natural-language violations, forcing a specific language without opt-in is a reportable issue unless the locale restriction is documented and justified.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The file’s natural-language content, including the top-level description and all reply/status messages, is written exclusively in Chinese. This imposes a language choice on users without any opt-in, fallback, or documented justification that the skill is intended only for a Chinese-speaking or region-specific audience.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The skill title and all usage examples are presented only in Chinese, including the direct invocation phrases. Because the document does not state that the skill is intended only for Chinese-speaking users or offer an alternative language/locale option, it may violate a language-choice policy for general-use skills.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The '/usage' command is overly generic and likely to collide with other commands or user intents related to usage statistics, billing, or system help. In a multi-skill or multi-command environment, such ambiguity increases the risk of unintended skill execution and user confusion, though the direct security impact is limited by the skill's read-only functionality.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The natural-language comments and skill description are written entirely in Chinese, including the user-facing purpose statement about querying token usage and warnings. Under the stated policy, forcing a specific language without offering a choice or documenting a justified locale constraint is a policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The skill’s user-facing description and output strings are entirely in Chinese, which can force a specific language/locale on users without opt-in. The file does not indicate that the skill is region-specific or that users can choose another language.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The package description is written only in Chinese, which can indicate a language-specific constraint without any opt-in or explanation. Under the policy, language/locale restrictions should either offer user choice or be clearly documented as justified for a region-specific use case.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 21)May include surrounding context.

json
"author": "Spark",
  "license": "MIT",
  "devDependencies": {
    "@types/node": "^20.0.0",
    "typescript": "^5.0.0"
  }
}

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
40% confidence
Finding

Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.

Content

Scanner excerpt · package.json (reported line 22)May include surrounding context.

json
"license": "MIT",
  "devDependencies": {
    "@types/node": "^20.0.0",
    "typescript": "^5.0.0"
  }
}