Back to skill

Security audit

Construction Estimator Pro

Security checks for vulnerabilities and agentic risk

Overview

This is a construction estimating reference skill with broad trigger wording but no hidden execution, persistence, credential access, or data exfiltration behavior.

Before installing, be aware the skill may activate for generic words like 'estimate' or 'bid'; users should specify construction context and independently verify cost assumptions before relying on estimates for financial decisions.

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
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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)

Vague Triggers

Medium
Confidence
93% confidence
Finding
The manifest uses very broad trigger terms such as 'estimate' and 'bid', which are common across many domains and can cause the skill to activate for unrelated requests. In an agent ecosystem, unintended invocation can route user data or decision-making into the wrong workflow, producing misleading outputs or unnecessary exposure of user context.

Natural-Language Policy Violations

Low
Confidence
72% confidence
Finding
L086 uses mandatory natural language requiring one standard for every estimate. While this is domain-oriented rather than geographic, it still imposes a single convention without offering opt-in, alternatives, or explanation of when exceptions apply.

Static analysis

No suspicious patterns detected.