Back to skill

Security audit

Frontend Security Review

Security checks for vulnerabilities and agentic risk

Overview

This is a frontend security review checklist skill that is transparent about inspecting code for common web security risks and producing a report.

Install this if you want a Chinese-oriented frontend security review workflow. Expect it to read relevant project code during review and create a Markdown report under reports/; ask the agent to respond in another language if needed.

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

Skill Enumeration

Medium
Category
Agent Snooping
Content
- ID: `fec-security-review`
- Category: `review-quality`
- Version: `2.6.0`
- Source: `skills/fec-security-review/SKILL.md`

## Description
Confidence
80% confidence
Finding
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Vague Triggers

Medium
Confidence
95% confidence
Finding
The skill's trigger text is broad enough to activate on many generic frontend review requests, which can cause the security-review skill to run outside its intended boundary. In agent systems, overbroad activation can misroute tasks, expose unnecessary context to the skill, and increase the chance of security-sensitive instructions being applied when the user did not explicitly request them.

Vague Triggers

Low
Confidence
79% confidence
Finding
The description says to use the skill when reviewing many frontend security topics and lists Chinese triggers such as '安全审查' and '安全检查'. These phrases are generic enough to overlap with routine security-review requests, and the file does not provide constraints, negative examples, or a narrower invocation context.

Natural-Language Policy Violations

Low
Confidence
79% confidence
Finding
The file presents the skill name and trigger terms in Chinese while other user-facing metadata is in English, but it does not state whether the skill is intended to operate in Chinese, English, or based on user preference. This can create an implicit language policy or user-experience constraint without explicit opt-in or documented locale behavior.

Natural-Language Policy Violations

Low
Confidence
84% confidence
Finding
The package description explicitly names Chinese trigger phrases alongside the English invocation guidance, but it does not state that language selection is optional or user-driven. Under the policy rule for language/locale handling, hard-coded language expectations can be a violation when no opt-in or justification is provided.

Natural-Language Policy Violations

Low
Confidence
91% confidence
Finding
This markdown template appears to require Chinese output throughout, including headings and report labels, but it does not state that the user can choose another language. That can violate a language/locale policy when a skill forces a specific language without user opt-in.

Natural-Language Policy Violations

Low
Confidence
92% confidence
Finding
This markdown file presents the entire skill content in Chinese and does not indicate that other languages are supported or that the language is user-selectable. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy concern.

Static analysis

No suspicious patterns detected.