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 Chinese-language reconciliation checker with no network, persistence, or hidden high-impact behavior found.
Install only if a Chinese-language outsourced-processing settlement checker fits your workflow. Treat the output as a local arithmetic reconciliation aid, not financial or legal advice, and note that the free tier explicitly omits several checks such as loss-rate-over-limit and contract-price mismatch review.
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 comments, user-facing advice, messages, disclaimer, and sample input are all written in Chinese, and there is no indication that the skill supports other languages or lets the user opt in to this locale. Under the policy rule, forcing a specific language without user choice is a natural-language policy violation unless the regional/language constraint is explicitly documented and justified.
The returned disclaimer says the tool performs table reconciliations '以及"明显偏高"的档位提示', which implies high-loss-rate prompting behavior. But the free-tier code in this file never evaluates LOSS_RATE_REF against row data and explicitly lists the loss-rate-over-limit check as withheld. This is an active contradiction between output documentation and actual behavior.
The user-facing description, usage text, prompts, and errors are entirely in Chinese, which effectively imposes a specific language on users. The file does not indicate that Chinese is optional, configurable, or justified as a region-specific constraint.
The activation description and trigger phrases are given only in Chinese, and the skill branding and usage text center a single language/locale experience. For an all-file policy check, this can be a natural-language locale constraint because the file does not offer an explicit user choice or opt-in for language despite also including English metadata elsewhere.
The file header states that CHECKS_WITHHELD is merely explanatory text and not an implementation. However, run() copies CHECKS_WITHHELD into scope.checks_not_run, making it part of the runtime result contract rather than just internal documentation. This is a mild documentation-to-code divergence, though it does not create extra execution capability.
The comment says non-JSON input is treated as plain-text material such as a '合同全文' (full contract text), which suggests broader accepted document types. However, the surrounding manifest and usage text consistently describe this skill as checking an outsourced-processing settlement sheet/table with headers, not general contract-text review. This is a documentation contradiction about the intended input scope rather than an implementation issue.
The JSON value at L2 consists entirely of Chinese headers and tabular content, with no indication that the skill supports other languages or that Chinese is an explicit, justified locale requirement. This can violate language/locale policy when a skill effectively forces a specific language without user choice.