ClawHub
Back to skill

Security audit

five-whys

Security checks for vulnerabilities and agentic risk

Overview

This is a small root-cause-analysis guidance skill with no executable code, persistence, credential handling, or hidden behavior.

Reasonable to install if you want structured Five Whys/postmortem assistance. Be aware it may ask the agent to read relevant logs, commits, tickets, timelines, and configs during an investigation, so use it in projects where that evidence access is appropriate.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 60)May include surrounding context.

md
- Jumping to a favorite cause and filling the chain backward to justify it.
- Asking "who" instead of "why". Blame ends the chain early; look for the missing safeguard.
- Single-chain thinking on a complex failure. Branch when there are several causes.
- Stopping at a cause nobody can change (for example "the vendor was down") without asking why there was no fallback.
- Treating `hypothesis` rows as findings in the summary.

Worked example: [references/example.md](references/example.md).

Static analysis

No suspicious patterns detected.