Back to skill

Security audit

Agent-Friendly Design

Security checks for vulnerabilities and agentic risk

Overview

This documentation-only skill gives agent-friendly web design guidance and does not include hidden code, persistence, or credential access.

Safe to install as a design-reference skill. Before applying its crawlability advice, decide which AI crawlers are appropriate for your site and avoid exposing private, user-specific, licensed, or regulated content without policy review.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The manifest description says the skill triggers on a long list including broad terms like "AX," "structured data," "JSON-LD," and "API-first design." These phrases are widely used in ordinary web-development conversations and are not specific enough on their own to clearly distinguish when this skill should or should not activate.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
78% confidence
Finding

The skill recommends allowing AI-specific crawlers in robots.txt as general guidance, but omits consent, privacy, contractual, and jurisdiction-specific constraints. In some deployments this could lead teams to expose content to third-party crawlers without appropriate policy review, increasing the risk of unintended data collection, indexing, or compliance issues.

Content

No source excerpt is available for this finding.