Back to skill

Security audit

Wedding.skill

Security checks for vulnerabilities and agentic risk

Overview

This is a wedding-planning helper that stores user-provided planning details locally, with privacy caveats users should understand before using it.

Install only if you are comfortable keeping wedding budgets, vendor contacts, guest details, dietary or mobility notes, and family/seating context in local plaintext files. Consider tightening filesystem permissions on ~/.wedding-skill/, avoiding unnecessary third-party sensitive details, and deleting or redacting records when planning is complete.

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:40
Finding

Plaintext Persistent Storage of Sensitive Wedding Planning Data

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 40–55, with sensitive-data examples and automatic reload behavior at lines 98–112, 127–138, and 282–287
Vulnerability Type: Plaintext storage of sensitive personal information without specified access controls
Risk Level: Medium

Vulnerable Code Snippets

markdown
All data stored locally. No cloud. No transmission.

\`\`\`
~/.wedding-skill/
└── [wedding-name]/
    ├── BUDGET.md              # Budget tracker with actuals vs planned
    ├── vendors.md             # All vendor details and deadlines
    ├── guests.md              # Guest list with RSVPs and seating
    ├── timeline.md            # Master timeline
    └── decisions-log.jsonl    # Every decision tracked
\`\`\`

- **Storage location**: `~/.wedding-skill/`
- **Format**: Markdown + JSONL (human-readable)
- **Cloud sync**: None
- **Deletion**: Remove the folder to delete all data

The documented records can contain personal contact and contract information:

markdown
Vendor: Blue Sky Photography
Contact: Sarah Chen — sarah@bluesky.com
Booked: March 15
Contract signed: March 20
Deposit paid: $1,500 (March 22)
Balance due: $2,000 (2 weeks before wedding)

Key terms:
- 8 hours coverage
- Second shooter included
- 500+ edited photos, delivered in 6 weeks
- Raw files NOT included (would be +$500)
- Cancellation: 50% refund if 60+ days out

They can also contain health-related and interpersonal information:

markdown
Dietary needs:
- 8 vegetarian
- 3 vegan
- 2 gluten-free
- 1 nut allergy (Sarah's cousin — FLAG for caterer)

Seating constraints you've told me:
❌ Uncle Mike CANNOT sit near Aunt Linda (the divorce)
❌ Your college friends need to be near the bar
❌ Boss should be at a visible table but not family table
✅ Grandma needs to be close to the exit (mobility)
✅ Kids table near the parents but with space for chaos

The memory rules require persistent reuse:

markdown
## Memory Rules

1. **Never overwrite** — e
...[truncated 2997 chars]
Remediation
View remediation

Remediation Suggestions

  1. Create ~/.wedding-skill/ with owner-only directory permissions (0700) and all data files with owner-only permissions (0600), explicitly overriding permissive process defaults.
  2. Provide authenticated encryption at rest for guest, vendor, financial, health-related, and family-conflict records. Store encryption keys separately using the operating system's secure credential facility.
  3. Obtain explicit consent before retaining third-party contact, allergy, dietary, mobility, or interpersonal information.
  4. Minimize collection by storing only fields necessary for active planning. Avoid preserving free-form sensitive conversation details by default.
  5. Replace indefinite “never overwrite” retention with configurable retention periods, archival controls, and secure deletion.
  6. Support selective deletion and redaction by guest, vendor, category, or decision instead of requiring deletion of the entire directory.
  7. Do not automatically load every record in every session. Load only the minimum data relevant to the current request.
  8. Warn users that local backup, indexing, synchronization, and file-sharing software may copy plaintext records.
  9. Add permission validation at startup and refuse to process sensitive records if the storage directory or files are accessible to unintended users.
  10. Document a migration procedure that secures existing plaintext records and removes obsolete unsecured copies.
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 (3)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger 'Any money-related question' is very broad and overlaps with common conversation, making it unclear when Budget Mode should activate versus other modes. The document does not provide constraints, examples, or exclusion conditions to narrow the scope.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The phrase 'Vendor question or deadline approaching' is underspecified because 'vendor question' is broad and 'deadline approaching' does not define what time window qualifies. This ambiguity could lead to unexpected or inconsistent mode activation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

Using 'Wedding week' as the trigger does not clearly specify when activation starts or ends, such as 7 days before, the calendar week of the wedding, or some other period. This creates an ambiguous invocation condition without explicit constraints.

Content

No source excerpt is available for this finding.