Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md node scripts/run.mjs --sample # 先看内置样例(一张干净表,应报 0 条问题)
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local, read-only checker for Chinese government subsidy ledger tables and does not show network use, persistence, hidden code execution, or data exfiltration.
Install only if you are comfortable running a local Node-based checker on Chinese subsidy ledger text. It handles business/financial table contents locally and read-only, but its conclusions are limited to arithmetic and checklist completeness; it is not a legal, audit, eligibility, or policy decision tool.
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看内置样例(一张干净表,应报 0 条问题)
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看内置样例(一张干净表,应报 0 条问题)
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 先看内置样例(一张干净表,应报 0 条问题)
The skill uses 'env' capability that is not listed in its permissions. This may indicate deceptive intent or missing permission declarations.
The file’s top-level description, user-facing advice, and operational messaging are all written in Chinese, indicating the skill is designed to communicate in a fixed language. There is no natural-language indication that users may choose another language or that the locale restriction is optional or justified as a region-specific requirement.
The user-facing description, usage text, prompts, and outputs are entirely in Chinese, and the skill does not indicate any option to choose another language or locale. Under the policy, a skill that effectively requires a specific language without opt-in is a natural-language policy concern unless the constraint is explicitly justified as region-specific.
The manifest description says the trigger words 'include' two phrases, but it does not define the full trigger scope, when the skill should not activate, or any exclusion examples. This can make invocation behavior ambiguous, especially because one listed phrase is a symptom-style complaint rather than a tightly bounded command.
The comment says non-JSON content will be treated as plain-text material such as a 'full contract text', which broadens the apparent supported input beyond the manifest's stated scope of reconciling subsidy ledgers and acceptance-material comparison tables. The implementation does pass arbitrary plain text through to the engine, so the inline documentation suggests a wider intent than the declared skill purpose.
The JSON payload consists entirely of Chinese-language headers and status text, with no indication that language is selectable or optional. Under the policy for natural-language violations, fixed language content can be a locale-policy issue when the skill does not document user opt-in or justified regional scope.