Security audit

Database Engineering Mastery

Security checks for vulnerabilities and agentic risk

Overview

This is a database guidance skill with disclosed SQL and operations examples; it has some examples users should review carefully before applying to real databases.

Installers should treat this as a reference guide, not as automatically safe production code. Review generated SQL before running it, especially audit triggers, destructive maintenance commands, backup deletion, replication-slot changes, and emergency termination commands. Redact sensitive audit fields and restrict audit-table access if adopting the audit-log pattern.

A.I.G

Vulnerability Patterns

Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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 (1)

T09 · Insecure Skill Coding Practices

Warning

Location: SKILL.md:590
Finding: Generic Audit Trigger Stores Complete Sensitive Database Rows
Content: View full analysis
Remediation: View remediation

SkillSpector

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: 92% confidence
Finding: The trigger phrase is broad enough to match routine user requests about database help, which can cause the skill to activate unexpectedly outside a narrowly intended scope. In an agent setting, overly broad invocation increases the chance of prompt/skill hijacking, unintended tool use, or the agent following this skill instead of more appropriate task-specific controls.
Content: No source excerpt is available for this finding.

Vague Triggers

Low

Category: Not specified by scanner
Confidence: 82% confidence
Finding: The phrase 'Audit this database' is ambiguous because 'audit' can imply many actions, from passive review to active inspection, security assessment, or operational analysis. That ambiguity can lead an agent to invoke the skill in situations where the user did not intend its full behavior, increasing the risk of overreach or mis-scoped analysis.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.