T01 · Skill Instruction Hijacking
- Location
SKILL.md:34- Finding
Unscoped and Non-Disableable Agent Instruction Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a safety guardrail, but it takes broad control over agent actions and can automatically log or sync activity through an external CLI, so it needs review before use.
Install only if you want a session-wide safety gate that may block or slow ordinary write actions. Prefer local-only use first, verify the threshold-keel package source/version before installing, avoid setting KEEL_CLOUD_API_KEY unless you accept cloud storage of action logs, and understand that disabling the skill is documented as removing the skill file rather than issuing a chat command.
SKILL.md:34Unscoped and Non-Disableable Agent Instruction Hijacking
SKILL.md:126Automatic Cloud Synchronization of Broad Activity Logs
SKILL.md:15Unpinned and Unauditable Executable Package Dependency
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
canonical WAL formatting, or guaranteed forward compatibility with CLI/Cloud
features.** It is a behavioural safety layer, not a durable state system.
**Do not create `~/.keel/` directories, `store.json`, or WAL files in
instructions mode.** The CLI owns that state and creates it in a canonical
format via `keel init`. Agent-created files in `~/.keel/` may be incompatible
with the CLI and will cause verification failures if the user later installs it.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
| Show quarantine | Inspect directories | `keel quarantine` |
| Restore item | Move files back | `keel restore --item-id ITEM_ID` |
The `--action-file` flag is the preferred way to pass action JSON -- write the
JSON to a temp file and pass the path. This avoids shell quoting issues across
platforms. The `--action-json` and `--payload` flags also accept inline JSON
strings or `@filepath` references (e.g. `--payload @/tmp/action.json`).
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Type "keel status" for details.
```
3. If CLI not available:
- Do NOT create `~/.keel/` directories or files
- Greet:
```
🦞🔒 Keel active (instructions mode). Behavioural guardrails are live.
This markdown file explicitly lists user phrases that invoke skill behavior, including generic variants like "keel log", "keel wal", and especially natural-language forms such as "keel add policy [desc]" and "keel restore [item]". While prefixed with "keel," the file does not provide negative examples or boundary conditions clarifying when similar conversational mentions should not trigger command handling, which could lead to unintended invocation in ordinary discussion about Keel.
No suspicious patterns detected.