T01 · Skill Instruction Hijacking
- Location
SKILL.md:3- Finding
Broad Trigger Rules Hijack Coding Workflows and Suppress Result Review
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill dispatches coding work to a background Claude process with broad permissions and hard-coded external notifications, so it needs careful review before installation.
Install only if you control and trust the referenced dispatcher and notification hook, recognize the hard-coded Feishu/WeCom destinations, and are comfortable with background coding tasks. Prefer an approval-requiring permission mode, explicitly confirm the project directory and notification recipient for each run, and review task outputs or diffs before relying on the result.
SKILL.md:3Broad Trigger Rules Hijack Coding Workflows and Suppress Result Review
SKILL.md:83Delegated Coding Tasks Default to Unrestricted Permission Bypass
SKILL.md:47Task Completion Data Is Sent to Hard-Coded External Recipients
SKILL.md:64Mandatory Invocation of an Unbundled and Unverified Local Dispatcher
The trigger criteria are extremely broad and overlap with routine coding requests, causing this skill to auto-activate for a wide range of normal development tasks. In context, that is dangerous because activation leads users toward dispatching unattended external code-execution workflows rather than keeping work in the current controlled session.
The skill instructs use of unattended code modification with --permission-mode bypassPermissions as the default, but does not require a prominent warning or explicit informed consent from the user before launching autonomous changes. This is dangerous because users may unknowingly authorize broad file modifications and command execution in their project without understanding the trust and change-control implications.
The skill is designed to launch long-running background tasks with completion callbacks, which creates persistence beyond the immediate session. While persistence is part of the intended functionality, it becomes security-relevant because it enables deferred autonomous code generation/modification and off-session notifications that may continue after the user's active oversight ends.
Dispatch long-running coding tasks to Claude Code CLI with automatic callback notifications to Feishu/WeCom when complete.
Use this skill whenever the user wants to:
- Create a new project or application from scratch
- Modify/upgrade an existing project with new features
- Refactor or improve existing code
- Run any coding task that might take a long time
Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.
Common issues:
1. **Working directory doesn't exist** - Create it first with `mkdir -p`
2. **Nested Claude Code session** - Can't run Claude Code inside Claude Code. User should run from a regular terminal.
3. **Permission denied** - Check if dispatch script is executable: `ls -l ~/openclaw/scripts/dispatch-claude-code.sh`
### Checking system status
Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.
# Check if hook is installed
ls -la ~/.claude/hooks/notify-agi.sh
# Check if dispatch script exists
ls -la ~/openclaw/scripts/dispatch-claude-code.sh
Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.
# Check if hook is installed
ls -la ~/.claude/hooks/notify-agi.sh
# Check if dispatch script exists
ls -la ~/openclaw/scripts/dispatch-claude-code.sh
The skill explicitly recommends autonomous operation modes such as dontAsk and defaults to bypassPermissions, normalizing execution and editing behavior without interactive approval. In a coding-dispatch skill that can modify arbitrary project files, this increases the chance of unintended destructive changes, unsafe commands, or execution beyond what the user expected.
Choose based on the task:
- `bypassPermissions` - No prompts, fully automated (recommended default)
- `dontAsk` - Run without asking, but still show what's happening
- `acceptEdits` - Safer for critical codebases, but requires some interaction
Default to `bypassPermissions` unless the user expresses concern about automated changes.