ClawHub

Plan Mode

v3.0.4

Think-first execution with approval gating. Use when work is complex, ambiguous, irreversible, multi-step, worth comparing before choosing, interrupted and n...

⭐ 1· 117·1 current·1 all-time
by@pieterjanliekens
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name, description, and SKILL.md consistently describe a read-first planning stance (clarify → plan → approve → execute) and the allowed actions (reads, listing, searching) match that purpose. No unrelated credentials, binaries, or installs are requested.
ℹ
Instruction Scope
The runtime instructions explicitly limit the agent to read-only exploration until user approval, and specify what to do in each lens. The included references mention a 'toolbox audit' (scan installed skills, search ClawHub/GitHub) — which implies potential external registry or network lookups and checks of installed skills. This is reasonable for avoiding reinventing functionality, but it could cause the agent to perform network queries or inspect installed-skill metadata unless the runtime restricts that. The SKILL.md does not instruct any destructive actions prior to approval.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. Low install risk.
✓
Credentials
No environment variables, credentials, or config paths are required. The skill's needs are proportional to its planning purpose.
ℹ
Persistence & Privilege
The skill supports creating 'living' plan files but explicitly requires explicit user approval before persisting. It is not always-on. Autonomous invocation is allowed (platform default) but not combined with other concerning privileges in this skill.
Assessment
This skill appears coherent and low-risk: it instructs the agent to be read-only until you explicitly approve execution or persistence. Before installing, confirm runtime policies about network access and file writes: if you don't want the agent to query external registries (ClawHub/GitHub) or write plan files (e.g., docs/plans/), restrict network/file permissions or verify the agent will ask before performing those actions. Also review agent logs or audit prompts during the first uses to ensure plans are only persisted or actions performed after your explicit approval.

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

latestvk97277pjkqsz1bcf08yktgrhvn846xww

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments