Skill flagged — suspicious patterns detected

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

Ai Plan Generator

v2.1.1

Generates comprehensive campaign documents, task decompositions, and context documents from minimal input for ClawTeam continuous iteration. Supports Code Ar...

1· 99·0 current·0 all-time
byroboe@hickhe
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name/description (AI plan generation + Code Archaeology integration) is consistent with included JS/Python code and the declared required binaries (node, git, bash). However multiple code files are tightly tailored to a specific Code Archaeology output naming scheme (zbs_php_*) and enterprise conventions (dms-erp, zbs_php). That degree of hard-coding to a particular project/format is narrower than the generic description and could surprise users expecting a broadly reusable tool.
!
Instruction Scope
SKILL.md directs the agent to run ai-plan-generator CLI with a user-specified archaeology path (expected). But the included Python and JS code also reference absolute/local paths and filenames outside the provided input (not declared in requires/config): e.g., ai_plan_generator_v2.py checks /Users/admin/.openclaw/workspace/zbs_php_security_audit_results.md and the integrator expects specific zbs_php_*.md filenames. These hard-coded reads of a user's workspace are not documented in SKILL.md and expand the skill's data access beyond the minimal input described.
Install Mechanism
No install spec is provided (instruction-only install behavior), and the package just requires common system binaries (node, git, bash). No external downloads or archive extraction are present in the manifest — this is low risk from an install-supply perspective.
Credentials
The skill requests no environment variables or credentials, which is proportional and reduces secret-exfiltration risk. However, code inspects specific local file paths (user workspace) and assumes enterprise integration defaults (e.g., default integration configs and domain assumptions). That implicit access to local files is not declared as required config paths and therefore is disproportionate to the advertised minimal-input model.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide persistence or modification of other skills. Autonomous invocation is allowed (platform default) but not combined with other high-privilege requests.
What to consider before installing
This skill appears to do what it says (generate campaign, task, and context documents from Code Archaeology output), but it contains hard-coded, user-specific filesystem references and strong defaults for a particular legacy project (zbs_php / dms-erp). Before installing or running it: 1) Inspect the code (especially ai_plan_generator_v2.py and code-archaeology-integrator.js) for any absolute/hidden paths and decide whether they should be removed or made configurable; 2) Run it in a sandboxed environment or with a throwaway user account to observe what local files it reads; 3) Provide only intended archaeology directories on the command line rather than relying on any implicit defaults; 4) If you rely on this for different projects, consider requesting the author generalize the zbs_php-specific filename expectations; 5) If you are uncomfortable with the tool reading your workspace, do not install it or edit the source to remove the hard-coded paths. Additional information that would reduce concern: confirmation that at runtime the tool only reads directories explicitly passed by the user (no fallback to /Users/admin or other user-specific paths) and configurable file-name patterns instead of hard-coded zbs_php_* filenames.

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

latestvk9731e4e06jdgde994nytv4h9h83m3eq

License

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

Runtime requirements

📋 Clawdis
OSmacOS · Linux · Windows
Binsnode, git, bash

Comments