Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent usage monitor, but it asks users to store and resend full dashboard URLs that may contain sensitive account or session data.
Install only if you are comfortable keeping the configured dashboard URL and generated usage log local. Do not paste URLs containing access tokens, signatures, session IDs, passwords, or sensitive query parameters; prefer an HTTPS, stable, non-secret dashboard URL. Avoid sending alert messages with the full dashboard URL unless all recipients should see it, and add your own .gitignore entries for config.json and usage-log.md before using the skill in a repository.
check.js:137Potentially Sensitive Dashboard URLs Are Persisted and Propagated Without Sanitization
The installation guide explicitly tells users to paste the full browser URL of a usage/quota dashboard into config.json. Such URLs commonly contain account identifiers, workspace IDs, query tokens, session artifacts, or other sensitive parameters, and the guide provides no warning to sanitize or avoid storing secrets in plaintext. In the context of a user-configurable monitoring skill, this increases the chance of credential leakage via local files, backups, screenshots, or accidental sharing.
The skill documentation is written entirely in Chinese, beginning with the description at L03 and continuing through the usage instructions and configuration details. Under the policy rules, forcing a specific language without user opt-in or a documented region-specific justification is a natural-language policy violation.
The title and core description are presented in Chinese, which imposes a specific language on users. The policy allows locale constraints only when the skill offers user choice or clearly documents and justifies the constraint, which is not present here.
The file’s user-facing natural-language instructions, labels, and comments are written exclusively in Chinese, including the title and configuration guidance. This imposes a specific language/locale on users without any opt-in, fallback, or explanation that the tool is intended only for a Chinese-speaking or region-specific context.
This JSON manifest/config schema contains natural-language descriptions exclusively in Chinese across multiple fields, but does not indicate that the skill is China/Chinese-specific or provide any user language opt-in. Under the stated policy, forcing a specific language without user choice is a natural-language policy issue applicable to all file types.
The user-facing content in this template is entirely in Chinese, including the warning and placeholder text, with no indication that the skill is region-specific or that users can opt into another language. This is a natural-language locale policy concern because it imposes a language choice by default rather than offering flexibility or justification.
A language/locale policy issue exists when a skill forces a specific language without user choice or justification. This installation document presents all operational instructions only in Chinese and does not offer an alternative language, opt-in, or note that the skill is intended only for a Chinese-speaking audience.
The file presents all user-facing guidance in Chinese and does not indicate that other languages are available or that Chinese is optional. This can violate a language/locale policy when a skill forces a specific language without user opt-in.
This manifest-style JSON example contains all instructional natural language in Chinese, including the top-level comment and field notes. Because no language choice or locale justification is provided, it imposes a specific language on users and matches the policy category for language or locale violations.