T01 · Skill Instruction Hijacking
- Location
SKILL.md:145- Finding
Mandatory Third-Party Branding Directives Manipulate Generated Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mainly a p5.js generative-art helper, but it forces Anthropic-styled branding into generated artifacts and uses remote browser code without integrity checks.
Review this skill before installing if you do not want generated work to preserve Anthropic-styled UI. For shared or hosted artifacts, consider removing the branding requirements and adding SRI or vendored copies for p5.js and fonts, especially if the HTML will be hosted alongside sensitive same-origin content.
SKILL.md:145Mandatory Third-Party Branding Directives Manipulate Generated Output
templates/viewer.html:23Remote JavaScript Dependency Executes Without Integrity Verification
The manifest description says to use this skill when users request 'creating art using code' or 'generative art,' which are broad, natural phrases that could match many unrelated creative coding requests. The file does not provide clear trigger boundaries, exclusions, or negative examples to limit when the skill should or should not activate.
The skill explicitly instructs the agent to read and reuse a branded HTML template verbatim and preserve fixed Anthropic-specific UI, fonts, colors, and structure. That creates a scope/identity risk: a skill intended for algorithmic art generation is also directing reproduction of proprietary-looking branding and exact product chrome, which can mislead users about endorsement and causes the model to copy non-user-authored template content beyond the core art logic.
The top-level description emphasizes originality to avoid copying existing artists' work. Later instructions explicitly require literal reuse of template HTML and unchanged branded UI sections, which conflicts with that originality framing at the documentation level even if the generative algorithm itself is meant to be unique.
The comments describe concrete functionality such as a p5.js generative art algorithm, particle system, and UI control handlers, but the corresponding functions and class bodies are placeholders with 'fill this in'. This is more than incomplete documentation because the file presents these sections as existing behavior while the code does not actually implement them.
No suspicious patterns detected.