Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

codex-orchestration

v2.0.0

General-purpose orchestration for Codex. Uses update_plan plus background PTY terminals to run parallel codex exec workers.

6· 3.9k·19 current·19 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name and description align with the SKILL.md: this is a coordinator/orchestrator guide for running parallel 'codex exec' workers and using PTY sessions. There are no unrelated env vars, binaries, or install steps requested.
!
Instruction Scope
The instructions assume the agent can run arbitrary commands via exec_command/write_stdin and manage background PTY sessions, create/read files (e.g. /tmp/w1.txt), and poll or restart processes. The guide explicitly recommends 'YOLO config (no approvals)' and suggests skipping git repo checks and using persistent runners (tmux/nohup). Those steps expand runtime capabilities beyond passive coordination and effectively instruct the agent to perform potentially high-privilege, system-level actions without safeguards.
Install Mechanism
No install spec or code files are present; risk from installation is minimal because nothing is written to disk by the skill itself.
Credentials
The skill requests no environment variables or credentials, which is proportionate. However, it advises changes to agent configuration ('YOLO', web search enabled, skipping repo checks) — these are not env vars but are operational directives that weaken normal safety controls and should be treated as sensitive configuration changes.
!
Persistence & Privilege
The skill does not set always:true, but it also does not disable model invocation. Given the instructions promote spawning background workers and running arbitrary commands, leaving model invocation enabled means the model could autonomously use those capabilities. That combination (model-invocable + guidance to run unchecked background processes) increases risk.
What to consider before installing
This skill is functionally coherent as an orchestration guide, but it contains operational recommendations that reduce safety (e.g., 'YOLO config', skipping git checks, running background PTY sessions and arbitrary commands). Before installing, consider: - Do you control the agent environment and enforce approvals? If not, do NOT enable 'no approvals' behavior. - Audit what exec_command and write_stdin actually do in your runtime: what permissions and host access they have, and whether they are logged. - Avoid running this on systems with sensitive data or production hosts where background commands could persist. - Prefer disabling autonomous model invocation for this skill (set disableModelInvocation: true) unless you explicitly want the model to spawn exec jobs without manual oversight. - Require an approval step / human review before any long-running or persistent worker starts; disallow skipping repo checks unless you understand the implications. If you want to reduce risk, ask the publisher for a version that removes the 'YOLO' guidance and explicitly limits execution to read-only, sandboxed analyses, or provide explicit safety checks (e.g., require a human confirmation before any exec_command that writes files or spawns persistent processes). Additional useful information to change this assessment: the skill's source/homepage, who maintains it, what the exec_command/write_stdin implementation enforces (sandboxing, user permissions, logging), and whether your agent platform enforces an approvals workflow regardless of the guidance in SKILL.md.

Like a lobster shell, security has layers — review code before you run it.

latestvk97fj51zn29e0wz1rb41j3s45n7ynqmz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments