Back to skill

Security audit

execute-specs

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed TDD workflow helper for implementing approved specs, with no evidence of hidden persistence, credential access, exfiltration, or destructive behavior.

Install this only if you want an agent to implement already-approved SPEC files using TDD, including editing code/tests and running validation commands. Be aware that progress messages will be in Portuguese and that the workflow is designed to proceed through approved slices without repeated approval prompts.

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
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • 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)

Lp3

Medium
Category
MCP Least Privilege
Confidence
70% confidence
Finding
Without declared permissions the skill's intent is opaque and cannot be validated.

Natural-Language Policy Violations

Medium
Confidence
97% confidence
Finding
The skill mandates that all user-facing communication be in Portuguese without checking the user's language preference. This can cause user confusion, misinterpretation of implementation or validation steps, and reduced transparency during code-changing workflows, which is a meaningful safety issue even if not a classic exploit vector.

Static analysis

No suspicious patterns detected.