ClawHub
Back to skill

Security audit

Building Permit & Construction Permitting

Security checks for vulnerabilities and agentic risk

Overview

This is a plain construction-permitting reference skill with no executable code, persistence, credential handling, or hidden authority.

Before using this skill for real permitting decisions, provide the project type and exact jurisdiction, then confirm requirements with the local building department or licensed professional. No special security precautions are indicated beyond treating the fee and compliance guidance as general reference material.

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 (1)

Vague Triggers

Medium
Confidence
87% confidence
Finding
The activation condition is broad enough to trigger on many general permit-related queries, which can cause the skill to engage outside narrowly intended construction-building contexts. This is primarily a scope-control issue: unintended invocation can lead to irrelevant or overconfident guidance, especially because permitting rules are highly jurisdiction-specific and mistakes may mislead users into compliance errors.

Static analysis

No suspicious patterns detected.