Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Agent CLI (Cursor + Qoder)
v3.0.0代码编辑 CLI 工具集合：Cursor CLI（agent）与 Qoder CLI（qodercli）。当用户需要修改代码、重构、Code Review、自动化代码任务时使用。
⭐ 0· 14·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (CLI wrappers for Cursor and Qoder) align with the instructions: both are TUI code-agent CLIs and the SKILL.md explains when to use each. However the included reference docs mention API keys (e.g., CURSOR_API_KEY) and config files (~/.qoder/*.json) even though the skill declares no required environment variables — a mild mismatch between declared requirements and referenced usage.
Instruction Scope
The runtime instructions specifically require creating a tmux PTY and sending commands into a TUI (correct for these CLIs) and tell the agent to cd into project paths and capture pane output. This naturally permits the invoked CLIs to read/write project files, run shell commands, and access networked services (per Qoder/Cursor features). The SKILL.md asks to inform the user beforehand, but it does not enforce or document explicit permission/limits for file or network access when the CLI runs.
Install Mechanism
The skill is instruction-only (no install spec), which is low-risk itself. But the bundled reference docs recommend network installers (curl https://cursor.com/install | bash, Homebrew cask, and npx installs for Qoder MCP plugins). Those are common for CLIs but do involve downloading and executing code from the network — a moderate installation risk the user should validate (verify official URLs/signatures).
Credentials
The skill declares no required environment variables, yet the references explicitly show CURSOR_API_KEY and config files (~/.qoder/settings.json, ~/.qoder/AGENTS.md, project-level .mcp/.qoder files). That mismatch means the skill may rely on credentials/config that aren't declared to the agent platform; installing or running the CLIs could require providing secrets in env/config files. The references also mention options like a '--yolo' flag that can skip permission checks — a dangerous option if used without oversight.
Persistence & Privilege
always:false and no install spec means the skill does not request forced persistent inclusion. It does not attempt to modify other skills or system-wide agent settings in the files provided. However, the invoked CLIs themselves (Cursor/Qoder) can persist memories/config in user files (AGENTS.md, ~/.qoder/), which is expected but worth auditing.
What to consider before installing
This skill is coherent with its stated purpose: it tells the agent how to run Cursor and Qoder TUI CLIs via tmux. Before installing or running it, verify the official sources and installers (e.g., cursor.com, docs.qoder.com), avoid piping unknown curl scripts to bash unless you trust the site and can verify signatures, and be aware that running these CLIs gives them the ability to read/write project files, run shell commands, and contact network services. Check whether you need to provide API keys (CURSOR_API_KEY or Qoder credentials) and store them securely; prefer least privilege, review ~/.qoder and project-level permission settings (deny or ask for sensitive paths), avoid the '--yolo' or equivalent flags in automated runs, and consider running first in an isolated environment (container or throwaway VM) to observe behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk9792wcdbtgpnw2ccm8b52pkph849t0n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.