Security audit
Security checks for vulnerabilities and agentic risk
This skill is a local business worksheet checker with no evidence of network access, credential use, persistence, or automatic file modification during its documented use.
Install only if you are comfortable giving the skill local read access to the institution materials you point it at. Use the documented node scripts/run.mjs commands for checking, treat outputs as reconciliation aids rather than audit or policy opinions, and avoid running rebuild_free.py unless you are maintaining the package source.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
If the implementation is only a vehicle-insurance amortization subset, then the skill's package-wide claims are misleading. In business-ops contexts, such mismatch can produce incorrect internal controls or reconciliation sign-off.
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 单机构样例（内置）
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 单机构样例（内置）
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 单机构样例（内置）
Referenced artifact was not completely inspected
node scripts/run.mjs --sample # 单机构样例（内置）
The script writes to a package source file (FREE.write_text(...)) even though the skill manifest describes a local auditing/reporting tool, not a package-rebuilding utility with source modification capability. This mismatch means the skill exposes filesystem modification power that users and policy layers may not expect, increasing the risk of unauthorized file changes or supply-chain tampering if the script is invoked in an automated agent context.
The file is a self-described build/reconstruction script for regenerating a free package engine, which materially differs from the manifest's promised functionality of auditing institution materials across 14 industry topics. This kind of capability drift is dangerous because users, orchestrators, and reviewers may trust the package for one purpose while it contains tooling for modifying product artifacts, creating a supply-chain and transparency risk.
Writing rebuilt engine code back into the package source exceeds the manifest's implied read/analyze/report scope and gives the skill artifact-modification capability. In an agent ecosystem, this can be abused to alter code or outputs on disk, and it undermines trust that the skill is only performing local audits rather than mutating its own implementation or nearby files.
The natural-language user-facing instructions in the markdown body are almost entirely in Chinese, which effectively forces a specific language for users reading the skill documentation. Although a short English description exists in metadata, the operational guidance and usage details do not offer a language choice or indicate that the Chinese-only instructions are intentional for a specific audience.
The file's natural-language interface is entirely in Chinese, including the module docstring, usage instructions, status messages, and the --check help text. This imposes a specific language on users without any documented opt-in or language-selection mechanism, which matches the language/locale policy violation category.