ClawHub
Back to skill

Security audit

Roast My Code

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only humorous code review skill that is abrasive by design but does not add hidden execution, network access, persistence, or privilege.

Install this only if you want intentionally sarcastic, sometimes harsh code feedback. Use it with explicit consent in teams, mentoring, or workplace settings, and avoid pointing it at sensitive files unless you are comfortable sharing that code with the active agent session.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (2)

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill advertises 'merciless,' 'absolutely destroys,' and 'brutal' output without a clear warning about emotional tone, consent, or suitability for vulnerable users. Because the core behavior is intentionally harsh, lack of up-front warning can lead to distress, harassment complaints, or unsafe use in workplace/team settings where participants did not knowingly opt in.

Vague Triggers

Medium
Confidence
92% confidence
Finding
The invocation guidance is broad enough that the skill could be triggered in contexts where users did not explicitly ask for harsh comedic feedback, such as onboarding, random file review, or general code review. In a skill designed to produce intentionally abrasive output, weak trigger boundaries increase the chance of unwanted or inappropriate activation, which can cause user harm, poor UX, or accidental review of sensitive code in the wrong context.

Static analysis

No suspicious patterns detected.