Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/run.mjs --sample # 先看样例
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local utility meter and bill reconciliation checker whose behavior matches its stated purpose and does not show hidden network, persistence, credential, or destructive activity.
Before installing, confirm that Chinese-language output and the rule that blank base fees count as 0 fit your workflow. The skill runs locally and does not appear to send data out, but its conclusions are limited to the listed arithmetic checks and should not be treated as a full utility-rate audit.
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看样例
The file’s natural-language interface, contract descriptions, inputs, outputs, and user-facing messages are entirely in Chinese, implying the skill is intended to operate only in that language. There is no visible user choice, opt-in mechanism, or explicit justification that this is a China-specific or Chinese-only tool, which can violate language/locale policy requirements.
The file repeatedly states that when materials are insufficient, the tool must not reach conclusions and must not apply default values. However, amount recomputation silently treats a missing base fee as 0, which can produce a definitive mismatch or a false pass from incomplete data. In a billing-validation skill, this is an integrity issue: users may rely on incorrect audit results to dispute or approve utility charges.
The comment says non-JSON input is treated as plain-text material such as '直接粘贴的合同全文', but the rest of the file consistently describes the required input as a utility meter reading and billing reconciliation table with headers. This is an active documentation mismatch that could mislead users about acceptable input for the skill.
The JSON content at L2 contains user-facing tabular text and labels only in Chinese, with no indication that users can select another language or locale. This can violate a language-choice policy when the skill forces a specific language without opt-in or documented justification.