Back to skill

Security audit

public-records-paper-trail

Security checks for vulnerabilities and agentic risk

Overview

This is a plain Markdown guidance skill for public-records research, with no executable code or hidden system-level behavior found.

Installers should understand this skill may be invoked for broad 'what happened here' research questions. Review any public-records request before submission, since filing may disclose requester information, create correspondence with agencies, or involve fees, even though the skill itself contains no code or hidden access behavior.

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
  • 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
Category
Not specified by scanner
Confidence
93% confidence
Finding

The manifest description says to use the skill when a user asks "what happened at a site," "who knew what when," or wants documents behind a news story or decision. These are broad, everyday investigative phrases without clear boundaries or exclusion conditions, which could cause unintended invocation outside a narrowly defined public-records workflow.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.