Back to skill

Security audit

C++/CPP Code Style

Security checks for vulnerabilities and agentic risk

Overview

This is a C++ style-guide skill with no hidden code execution, persistence, credential handling, or unrelated data access.

Install this only if you want agents to apply this C++ style guide by default. Override it when a repository has its own style rules, especially around comment language or formatting changes.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
92% confidence
Finding

The skill description uses very broad activation language around general C++ coding style, which can unintentionally trigger on ordinary programming requests rather than a narrowly scoped task. This increases the chance that the agent applies style-governance behavior in contexts the user did not explicitly request, creating instruction interference and unexpected behavioral override.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The instruction "使用英文注释" forces a specific language for comments. Under the policy, language constraints should either provide user opt-in/choice or be clearly documented as necessary for a justified regional or organizational requirement, which is not present here.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.