ClawHub
Back to skill

Security audit

Engagement Retro

Security checks for vulnerabilities and agentic risk

Overview

This is a plain Markdown consulting retrospective skill that asks the agent to produce a close-out document, with no code, persistence, credential use, or automatic external actions.

Before installing, be aware that the skill may process sensitive client, pricing, margin, and relationship details that you provide. Use it with engagement information you are comfortable sharing with your agent, and review any generated testimonial, referral, renewal, or pricing recommendations before acting on them.

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 55)May include surrounding context.

md
- [ ] Do not skip the money question — "the client was happy" but you lost margin means change the pricing, not repeat it
- [ ] Do not write vague lessons — "communicate better" isn't actionable; "add a weekly written status" is
- [ ] Do not let the engagement end without asking for the testimonial/referral — now is the easiest it'll ever be
- [ ] Do not bury scope creep — name what you ate so the next SOW prevents it
- [ ] Do not treat the retro as internal-only — the client-facing close-out also sets up the renewal

Static analysis

No suspicious patterns detected.