meta-toolchain-orchestrator@1.0.0
CAUTION· static onlyPublisher claims: "由 model-distillation 从教师技能 toolchain-orchestrator 蒸馏并增强的超越型元技能, 在教师能力之上叠加自验证、自我反思、super-agent 编排与持续自进化闭环,逐步超越教师。" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-09 and scored it 69/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
…# 来源能力签名(教师) - 标题层级:多步工具链编排引擎(toolchain-orchestrator), 能力依据(主流研究/框架), 链定义(chain.json), 标准工作流, 1. 校验(依赖存在/成环/命令可达), 2. 先看执行计划(拓扑序), 3. 真正执行(上游 stdout 通过 {{node_id}} 透传;日志在 outputs/run_log.json), 4. 某步失败后,修复该节点脚本,从它续跑 - 显性工作流步骤(0 步): (教师未显式编…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.No other findings across 155 lines in 5 files.
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
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim qq435912743: 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.