Lobster Subagent Dev
v1.0.0Subagent-driven development. Dispatch fresh subagent per task with 2-stage review (spec + quality). Cost-aware model routing. From Superpowers by Jesse Vincent.
⭐ 0· 29·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (subagent-driven development with 2-stage review) match the SKILL.md content. The skill is instruction-only and requires no binaries, env vars, or installs, which is proportionate to a process/workflow orchestration skill.
Instruction Scope
SKILL.md contains high-level orchestration steps (extract tasks, dispatch implementer/spec/quality reviewers, handle statuses). It does not instruct the agent to read unrelated files, access secrets, call unexpected external endpoints, or perform system-level operations. The instructions are procedural but remain within the stated coordination scope.
Install Mechanism
No install spec and no code files — lowest-risk model for an instruction-only skill. Nothing will be written to disk or downloaded by the installer.
Credentials
The skill requires no environment variables, credentials, or config paths. There are no requests for unrelated secrets or broad access, which is proportional to the described functionality.
Persistence & Privilege
always is false and there is no indication the skill modifies other skills or system-wide settings. Autonomous invocation is allowed by platform default, which is expected for an orchestration skill; the skill does not request elevated persistence or privileges.
Assessment
This skill is internally coherent and low-risk as provided: it only defines a workflow for dispatching short-lived subagents and requests no secrets or installs. Things to consider before enabling: (1) subagent autonomy — ensure you trust automated dispatching and review the agent's authorization policy for launching subagents; (2) cost/model routing — confirm which models will be used for each task type to avoid unexpected expense; (3) validation — because the process delegates work, make sure human review gates and test-run policies are enforced so automated subagents cannot merge or deploy changes without oversight. If you want stricter controls, restrict the skill to user-invocable only (no autonomous runs) or configure model/endpoint allowlists and rate/cost limits.Like a lobster shell, security has layers — review code before you run it.
latestvk9795axrz0b13qh77g6tcxp83d847q2y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.