Back to skill

Security audit

Context Monitor Helper

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed local context-usage meter; it does not show hidden data exfiltration, persistence, or destructive behavior.

Install only if you are comfortable with a skill seeing the current session history locally to estimate token usage and appending Chinese context-status text to replies. Developers should refresh the dev dependency lockfile before running build or test tooling on untrusted inputs.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (20)

Known Vulnerable Dependency: brace-expansion==1.1.13 — 3 advisory(ies): CVE-2026-13149 (brace-expansion: DoS via exponential-time expansion of consecutive non-expanding); CVE-2026-14257 (brace-expansion: DoS via unbounded expansion length causing an out-of-memory pro); CVE-2026-69152 (brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-1)

High
Category
Supply Chain
Confidence
93% confidence
Finding

brace-expansion 1.1.13 is a confirmed vulnerable version with multiple denial-of-service issues involving exponential or unbounded expansion behavior. Even though it is a transitive dev dependency, these parser/expansion flaws can be triggered by crafted patterns and may exhaust CPU or memory in tooling paths that process glob-like input, which is more serious than a mere informational finding.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: browserslist==4.28.2 — 2 advisory(ies): CVE-2026-73088 (Browserslist: Uncaught crash / prototype write via untrusted browserslist-stats.); CVE-2026-73089 (Browserslist: Unbounded memory growth (no cache eviction) via distinct query res)

High
Category
Supply Chain
Confidence
88% confidence
Finding

browserslist 4.28.2 is flagged for crash/prototype write and unbounded memory growth issues when handling untrusted stats or distinct query inputs. In this repository it is only used in dev-tooling dependency chains, which reduces exposure, but if CI/build automation ingests untrusted browserslist configuration or stats files, the impact can include denial of service and possibly unsafe object mutation.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: js-yaml==3.14.2 — 4 advisory(ies): CVE-2026-84375 (js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources); CVE-2026-59869 (js-yaml: YAML merge-key chains can force quadratic CPU consumption); GHSA-5p4m-2wfm-xmqj (JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026) +1 more

High
Category
Supply Chain
Confidence
94% confidence
Finding

js-yaml 3.14.2 has multiple CPU-consumption issues involving merge keys and complex YAML structures, making it vulnerable to denial of service when parsing attacker-controlled YAML. Although present as a development dependency, YAML parsers are commonly reachable in configuration-loading code paths, so malformed input could significantly slow or stall developer or CI environments.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The entire skill documentation is written in Chinese, including setup, commands, warnings, and FAQs, with no indication that users may choose another language or that the skill is intended only for a Chinese-speaking or region-specific audience. Per the policy, forcing a specific language without opt-in is a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill title and behavior description are written entirely in Chinese and describe automatic additions to every reply, but there is no indication that the language is optional or limited to a Chinese-only deployment context. This can violate language/locale policy expectations when users have not opted into Chinese output.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The file description and all user-facing status/warning strings are written only in Chinese, indicating the skill forces a specific language experience. Under the policy, locale-specific behavior should either offer user opt-in/choice or be clearly justified as region-specific.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The warning, recommendation, status, and enable/disable messages returned to users are all fixed Chinese strings. There is no indication that users can choose their language or that the skill is intentionally limited to a Chinese-language environment.

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 specifies the skill will display reminders in that language, with no indication that users can choose another language or locale. This creates a natural-language policy concern because it appears to impose a specific language experience without explicit opt-in or documented regional justification.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The user-facing description and status/warning strings in this file are exclusively Chinese, which effectively forces a specific language/locale. The file does not indicate that the skill is region-specific or provide any opt-in or fallback for users in other languages.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The test requires the generated status message to contain the Chinese term "立即", which semantically enforces a specific locale in skill output. This is a natural-language policy concern because the file does not indicate that users can choose language or that the Chinese-only behavior is intentionally limited to a justified region-specific context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

The natural-language comments describe the skill exclusively in Chinese and do not indicate that the user can choose another language or that the skill is intentionally limited to Chinese-speaking users. This can violate a language/locale policy when users are not given an explicit opt-in or justified locale constraint.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

The module documentation describes a skill that 'real-time monitors context usage' and displays usage information, implying passive monitoring behavior. However, the main handler also implements '/context on' and '/context off' control commands, yet these only mutate a fresh local config object for the current invocation and therefore do not actually enable or disable ongoing monitoring as the comments suggest.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: @babel/core==7.29.0 — 1 advisory(ies): CVE-2026-49356 (@babel/core: Arbitrary File Read via sourceMappingURL Comment)

Low
Category
Supply Chain
Confidence
82% confidence
Finding

The lockfile pins @babel/core 7.29.0, which is flagged for an arbitrary file read issue via sourceMappingURL parsing. In this skill context it is a development-only transitive dependency used by Jest/Babel tooling, so exploitation would typically require processing attacker-controlled source content during build/test workflows, making the practical risk lower but still real.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: baseline-browser-mapping==2.10.14 — 1 advisory(ies): CVE-2026-45819 (baseline-browser-mapping process termination on invalid input causes denial of s)

Low
Category
Supply Chain
Confidence
76% confidence
Finding

baseline-browser-mapping 2.10.14 is reported vulnerable to process termination on invalid input, which can lead to denial of service. Here it appears only as a dev dependency transitively pulled by browserslist tooling, so the issue is unlikely to affect runtime behavior of the skill but could disrupt local or CI build processes if given malformed input.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

The natural-language description is written entirely in Chinese and presents the skill behavior without offering any language or locale choice. Under the stated policy, forcing a specific language without user opt-in can be a language/locale policy violation unless clearly justified as region-specific.

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 25)May include surrounding context.

json
"author": "Spark <zhengyuhang@example.com>",
  "license": "MIT",
  "devDependencies": {
    "@types/jest": "^29.5.12",
    "@types/node": "^20.11.5",
    "jest": "^29.7.0",
    "ts-jest": "^29.1.2",

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 26)May include surrounding context.

json
"license": "MIT",
  "devDependencies": {
    "@types/jest": "^29.5.12",
    "@types/node": "^20.11.5",
    "jest": "^29.7.0",
    "ts-jest": "^29.1.2",
    "typescript": "^5.9.3"

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 27)May include surrounding context.

json
"devDependencies": {
    "@types/jest": "^29.5.12",
    "@types/node": "^20.11.5",
    "jest": "^29.7.0",
    "ts-jest": "^29.1.2",
    "typescript": "^5.9.3"
  },

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 28)May include surrounding context.

json
"@types/jest": "^29.5.12",
    "@types/node": "^20.11.5",
    "jest": "^29.7.0",
    "ts-jest": "^29.1.2",
    "typescript": "^5.9.3"
  },
  "engines": {

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 29)May include surrounding context.

json
"@types/node": "^20.11.5",
    "jest": "^29.7.0",
    "ts-jest": "^29.1.2",
    "typescript": "^5.9.3"
  },
  "engines": {
    "node": ">=18.0.0"