Security audit
Security checks for vulnerabilities and agentic risk
This is a local procurement and payables checking skill that reads user-provided business files and reports findings without network use, file writes, persistence, or hidden privilege behavior.
Install only if you are comfortable running a local checker over procurement, payables, contract, invoice, and reimbursement text you provide. Review the output fields listing checks not run and sub-checks not run, and do not treat a clean result as an audit opinion or proof that payments, contracts, invoices, or accounting treatment are valid.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
The documentation itself acknowledges free-vs-full differences and withheld checks, yet still presents the skill as a complete 14-check pack, which can confuse users about what was actually executed. Because this is a local business-control tool, the primary risk is deceptive completeness leading to missed exceptions rather than external attack.
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 file explicitly states it is only a free-tier subset that runs 6 checks and withholds 5 additional checks, while the skill metadata promises broad 14-item procurement/payables coverage. In an audit or finance workflow, this mismatch can cause users to rely on incomplete control results, creating a false sense of assurance and potentially missing material accounting issues.
The code and comments explicitly state that several payable-provisional checks advertised in the broader skill description are withheld and never executed, yet the engine still returns them as part of the surfaced capability metadata. In an audit or finance workflow, this creates a dangerous false sense of coverage: users may rely on the tool to detect overdue reversals, unmatched invoices, or stale accruals when those checks are in fact absent.
The file header explicitly narrows behavior to a local 'free tier' six-check contract consistency engine, while the skill metadata promises a broader 14-item procurement/payables audit workflow. This mismatch is dangerous because users may rely on the advertised coverage for financial control review and falsely believe required checks were performed when they were silently omitted.
The run() path returns a service type of 'CONTRACT_CONSISTENCY_FREE', lists only six checks, and marks other checks as withheld, which directly contradicts the skill's advertised end-to-end procurement/payables review scope. In an audit context, this can cause under-auditing, missed exceptions, and incorrect compliance or accounting conclusions because the output looks authoritative despite limited coverage.
The manifest describes a broad skill that locally audits procurement and payable working papers across 14 named checks, with per-object conclusions and source line references. This file implements only an expense reimbursement precheck subset: duplicate invoice number detection, invoice field completeness, and placeholder detection, while explicitly listing many expected reimbursement checks as withheld and not implemented.
The natural-language guidance and user-facing strings throughout the file are exclusively in Chinese, including operational instructions and disclaimers. There is no indication that the skill is region-specific or that users may opt into another language, which can violate language/locale policy requirements.