Back to skill

Security audit

architecture-paradigm-service-based

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only architecture guidance skill with no execution, data access, or persistence, though a couple of triggers are broad enough to activate more often than intended.

Install only if you want service-based architecture guidance to appear during architecture discussions. Be aware it may activate on broad words like `architecture` or `modular`, so narrower triggers would improve relevance.

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
95% confidence
Finding

The trigger phrase 'architecture' is extremely broad and likely to match many unrelated conversations, causing this skill to activate outside its intended service-based architecture context. Overly broad activation can inject irrelevant architectural guidance into unrelated tasks, reducing reliability and potentially steering users or agents toward unintended actions.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger 'modular' is ambiguous and context-poor, so it may invoke this skill during unrelated discussions about code organization, package structure, or general design principles. This increases accidental activation risk and can cause inappropriate guidance to be surfaced when the user did not intend to request this specific architectural paradigm.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.