Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed database-operations playbook that stores optional local context and emphasizes user confirmation for risky database actions.
Install only if you want a persistent local database operations notebook. Keep secrets, passwords, connection strings, and private keys out of ~/database-manager/, and review any proposed production database action before approving it.
Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.
- define one guardrail per failure mode
- schedule follow-up validation date
Incident closure without guardrails invites repeat failures.
The skill instructs the agent to capture and store operationally sensitive environment details such as database engines, critical systems, data domains, and recovery targets. Persisting this information in local memory increases the risk of unnecessary retention and later disclosure of infrastructure and business-critical metadata, especially if the stored context is broader than needed for the active task.
## Baseline Context to Capture
Capture context that improves future decisions:
- Main database engines and versions in use
- Critical systems and data domains
- Recovery objectives (RTO and RPO targets)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
mkdir -p ~/database-manager/archive
touch ~/database-manager/{memory.md,inventory.md,standards.md,migrations.md,backups.md,incidents.md}
chmod 700 ~/database-manager
chmod 600 ~/database-manager/{memory.md,inventory.md,standards.md,migrations.md,backups.md,incidents.md}
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
mkdir -p ~/database-manager/archive touch ~/database-manager/{memory.md,inventory.md,standards.md,migrations.md,backups.md,incidents.md} chmod 700 ~/database-manager chmod 600 ~/database-manager/{memory.md,inventory.md,standards.md,migrations.md,backups.md,incidents.md}
3. If `memory.md` is empty, initialize it from `memory-template.md`.
The activation boundaries say to 'Always activate for schema, migration, or query performance requests' while also saying to activate only when the user explicitly asks for database help. These conditions are ambiguous and broad enough to overlap with ordinary technical discussion, and they do not provide clear exclusions or negative examples to resolve when the skill should stay inactive.
No suspicious patterns detected.