shisan-xinuo-workflow@1.0.20
CAUTIONPublisher claims: "纪律元工作流(核心):把任何工程任务强制按「三级跑道(L1 快速通道 / L2-S 短工作流 / L2-F 完整 9 步)+ L1/L2/L3 封闭清单速判 + 三模式」推进的可审计 Agent 纪律核心——管住「怎么做」(复述/判级/能力检索/门禁/证据/跳过声明);流程细节与审查角色按需加载(配套 shisan-xinuo-flows / shisan-xinuo-roles)。适用:任何动手工程任务——编码/多文件/跨模块/修 bug/建组件/审查/用户点名按流程;不适用:纯聊天问答、单文件只读查询、与工程无关的对话。" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zxc663: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.