T08 · Insecure Dependencies
Warning
- Location
prompts/Industrial.md:167- Finding
Unpinned Third-Party Carbon-Fiber Texture
- Content
View full analysis
- Remediation
View remediation
Security audit
Design Style
Security checks for vulnerabilities and agentic risk
Overview
This is a frontend design prompt library that reads local style guides; it has some broad styling and third-party asset recommendations but no hidden persistence or data-stealing behavior.
Install only if you want a broad frontend design-style prompt library. Review generated code before deploying, especially any Google Fonts imports, remote texture URLs, animation libraries, forced dark/light themes, uppercase text, or motion-heavy effects; replace external assets with local or approved resources for privacy-sensitive sites.
Vulnerability Patterns
- Insecure DependenciesIntroduces malicious components through unsafe dependency sources
- 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
Findings (2)
T08 · Insecure Dependencies
Warning
- Location
prompts/Web3.md:149- Finding
Unpinned Third-Party Cube Texture
- Content
View full analysis
- Remediation
View remediation
Vulnerability Patterns
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
- MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (19)
Tp4
High
- Category
- MCP Tool Poisoning
- Confidence
- 98% confidence
- Finding
There is a material mismatch between the broad declared purpose and the actual code behavior. The description promises a skill for building or improving frontend interfaces and selecting an appropriate design style prompt. However, the provided shell script merely inspects a local prompts directory, counts .md files, and prints their names plus a usage example. That is a supporting utility for discovering available styles, not the core functionality described. It accesses only local prompt files and performs no frontend generation, styling, framework integration, or prompt selection beyond listing filenames.
- Content
Tp4
High
- Category
- MCP Tool Poisoning
- Confidence
- 98% confidence
- Finding
The declared description says this skill should be used proactively for frontend/UI creation and styling work and that it retrieves appropriate design-system prompts to produce frontend code. The supplied code does not implement frontend generation, UI styling assistance, or prompt retrieval for user-facing design tasks. Instead, it is a maintenance/verification shell script for checking whether the skill is correctly configured on disk. That is a materially different primary purpose, so this is a clear description-behavior mismatch.
- Content
Vague Triggers
High
- Category
- Not specified by scanner
- Confidence
- 97% confidence
- Finding
The activation criteria are extremely broad, causing this skill to trigger on almost any frontend-related request. In an agent environment, overbroad auto-invocation can override more specific skills, pull in unnecessary prompt context, and increase the chance of instruction collision or unintended behavior across many normal user requests.
- Content
Hidden Instructions
High
- Category
- Prompt Injection
- Confidence
- 70% confidence
- Finding
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
- Content
Example: Vue 3 + Plain CSS
vue <!-- components/HeroSection.vue --> <!-- Using Neo-brutalism.md design system --> <template>
Vague Triggers
Medium
- Category
- Not specified by scanner
- Confidence
- 92% confidence
- Finding
The 'automatically invoked' conditions are ambiguous and insufficiently constrained, which can make the agent invoke this skill in contexts where design-style guidance is irrelevant or conflicting. That increases prompt-scope sprawl and can degrade safety by making routing less predictable, especially in multi-skill systems where broad triggers can hijack workflow selection.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 91% confidence
- Finding
The prompt states the palette is 'strictly light mode,' which imposes a display/locale-style preference on all outputs. Because the file does not present this as optional or user-selectable, it can violate policy against forcing a specific presentation preference without opt-in.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 92% confidence
- Finding
The prompt makes uppercase treatment mandatory for headings, buttons, and labels without allowing user preference, language context, or accessibility exceptions. While not a code-execution or data-security issue, this is a genuine accessibility and safety-of-output problem because it can degrade readability, pronunciation, localization quality, and assistive-technology usability across generated interfaces.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 96% confidence
- Finding
The instruction "Mode: Light (Permanent - no dark mode)" imposes a specific UI mode as a hard requirement. This is a natural-language policy concern because it forces a presentation preference without user opt-in or a documented region/compliance justification.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 89% confidence
- Finding
The prompt explicitly mandates marquee scrolling, blinking, pulsing, and rainbow animations as required style elements, which can produce motion-heavy or distracting UI without first warning the user or making reduced-motion behavior the default. Although the file later mentions
prefers-reduced-motion, the skill still strongly pushes sensory-intensive patterns and may cause the agent to generate inaccessible interfaces for motion-sensitive users unless the user actively objects.- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 91% confidence
- Finding
The prompt requires exclusively handwritten or marker-style fonts for all headings and body text, which can reduce readability, legibility, and accessibility for users with dyslexia, low vision, cognitive disabilities, or users expecting conventional UI typography. Because this is framed as a hard requirement rather than a stylistic preference with accessibility checks or user opt-in, the skill can systematically generate inaccessible interfaces across many outputs.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 80% confidence
- Finding
The design-system instructions explicitly require 'Dark Mode Only' and state that high contrast is non-negotiable, which forces a particular presentation choice rather than offering the user a choice. Under the policy rule for natural-language constraints, this is a style/locale-like mandate without opt-in or a clearly documented region/compliance justification.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The prompt hard-codes a single 'Dark Mode Only' Bitcoin/DeFi visual system and repeatedly frames it as mandatory, which can override user preferences, brand requirements, accessibility needs, or platform theming constraints. In a frontend design skill, this is risky because the model may confidently impose an unsuitable aesthetic rather than first confirming whether the user actually wants that style or needs light-mode/accessibility alternatives.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The prompt hard-codes use of the Google-hosted 'Outfit' font and explicitly specifies its import source without offering an opt-in or a self-hosted/privacy-preserving alternative. This can cause unnecessary third-party network requests, exposing user IP address, user agent, referrer, and page access metadata to the font provider, which is a real privacy issue even though it is not an exploit-oriented security flaw.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 82% confidence
- Finding
The instructions prescribe a single font family, 'Outfit', as mandatory design guidance. This can create a language/locale policy issue because a fixed typeface may not be appropriate for all scripts or regional typography needs, and the file does not offer user choice or note any locale constraints.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 82% confidence
- Finding
The prompt prescribes "Playfair Display" and "Inter" as the only fonts to use, and later reinforces this as a strict requirement. This can violate language/locale flexibility expectations because these Latin-centric typography choices may not be appropriate for all scripts or locales, and the file does not offer any user choice or documented regional justification.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 82% confidence
- Finding
The prompt specifies "Font Family: Roboto (Google Fonts) - The canonical Material Design typeface" as a fixed requirement. This imposes a specific language/script presentation choice without offering user opt-in or alternatives, which can conflict with locale/language policy expectations for multilingual contexts.
- Content
Intent-Code Divergence
Low
- Category
- Not specified by scanner
- Confidence
- 92% confidence
- Finding
The motion section states "NO translate/lift effects — too trendy for this timeless aesthetic" at L417, but earlier button guidance explicitly prescribes a subtle lift on hover with
-translate-y-0.5at L285 and later accessibility guidance again allows subtle shifts at L521. This is an internal intent/documentation contradiction about whether translate-based motion is part of the design system.- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 83% confidence
- Finding
The instruction mandates uppercase for almost all headings and labels as a fixed stylistic rule. This imposes a specific language presentation convention without offering user choice or noting exceptions for locale, accessibility, or content needs, which fits the policy concern around forced language/locale behavior in natural-language instructions.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 78% confidence
- Finding
The design system explicitly states "Dark Mode Only," which imposes a fixed presentation mode rather than offering the user a choice or opt-in. Under the policy criteria, forcing a specific mode/locale-style preference in natural-language instructions can be a policy concern when no alternative is provided.
- Content
Static analysis
Detected: suspicious.prompt_injection_instructions
Prompt-injection style instruction pattern detected.
Warn
- Code
- suspicious.prompt_injection_instructions
- Location
- SKILL.md:109