Back to skill

Security audit

Church Event Planner

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent church event planner, but it persistently stores and broadly loads sensitive volunteer and church operations data without enough scoping or user controls.

Review this skill before installing if your church stores real volunteer or member information. Use it only where local skill data is access-controlled, avoid entering sensitive health or pastoral notes unless necessary, and prefer explicit review before saving or displaying roster-wide data.

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

Plaintext Persistence and Overbroad Loading of Sensitive Volunteer Data

Content
View full analysis

Vulnerability Details

File Location: SKILL.md:20-126
Vulnerability Type: Plaintext sensitive-data storage and excessive data loading
Risk Level: Medium

Vulnerable Code Snippet

text
All event data is stored in a structured JSON file called `event-data.json` in the skill's data directory. This file is the single source of truth.
json
{
  "ministryTeams": [
    {
      "id": "team-id",
      "name": "Worship Team",
      "leadName": "Mike Roberts",
      "leadContact": "555-222-3333",
      "members": ["volunteer-id-1", "volunteer-id-2"],
      "ownsEvents": ["event-id"],
      "notes": "Rotates every other Sunday"
    }
  ],
  "volunteerRoster": [
    {
      "id": "vol-id",
      "name": "Sarah Johnson",
      "contact": "555-111-2222",
      "skills": ["snacks", "childcare"],
      "teams": ["team-id"],
      "blackoutDates": ["2026-07-01", "2026-07-08"],
      "preferences": "Mornings only. Allergic to nuts (relevant for snack roles).",
      "recentAssignments": [
        {
          "event": "VBS 2026",
          "role": "Snack coordinator",
          "date": "2026-06-15"
        }
      ],
      "burnoutScore": 2
    }
  ]
}
text
### Persistence Rules
- **Read first.** Always load `event-data.json` before responding.
- **Write after every change.** Any time data is added, updated, or removed, write immediately.
- **Create if missing.** If the file doesn't exist, create it with empty arrays on first use.
- **Never lose data.** Merge updates with existing records. Don't overwrite fields the user didn't mention.

Technical Analysis

The skill directs the agent to store all event and roster information in a single JSON file. The documented schema includes names, telephone numbers, church or team affiliations, availability dates, assignment history, and health-related constraints such as allergies.

No corresponding controls are defined for restrictive file permissions, encryption at rest, consent before storing ...[truncated 2560 chars]

Remediation
View remediation

Remediation Suggestions

  1. Apply data minimization

    • Load only the event, volunteer, vendor, or team records required for the current request.
    • Avoid placing the entire database in the active model context.
    • Separate operational event data from contact and health-related fields.
  2. Protect data at rest

    • Require owner-only permissions for the data directory and JSON file, such as mode 0700 for the directory and 0600 for the file on supported systems.
    • Use authenticated encryption for sensitive fields when the deployment threat model requires protection from local file disclosure.
    • Store encryption keys in the operating system credential store, not beside the encrypted data.
  3. Introduce authorization controls

    • Verify that the current operator is authorized before displaying roster-wide, contact, availability, or health-related information.
    • Default to redacted contact details in summaries.
    • Restrict bulk export and cross-team queries.
  4. Obtain consent and limit collection

    • Confirm before persisting personal contact or sensitive constraint data.
    • Record only information necessary for scheduling.
    • Avoid free-form notes for sensitive information when a less revealing structured flag is sufficient.
  5. Define lifecycle controls

    • Establish retention periods for completed events, assignment histories, and stale volunteer records.
    • Provide selective record deletion and secure export procedures.
    • Ensure backups receive protections equivalent to the primary datastore.
  6. Reduce secondary exposure

    • Prohibit sensitive values from being written to telemetry, debug logs, exception output, or model traces.
    • Redact unrelated records before constructing prompts or responses.
    • Add tests confirming that a request about one event cannot reveal records belonging to unrelated events or teams.
Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Behavioral ASTexec() Call, eval() Call, Dynamic Import
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (8)

Vague Triggers

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The activation text is excessively broad and includes ordinary conversational phrases like burnout checks, sermon alignment, and casual planning language, making accidental invocation likely. Because the skill reads and writes persistent event and volunteer data, unintended activation can expose or modify sensitive operational and contact information without the user clearly intending to use this skill.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger phrase "What's coming up?" is broad and commonly used in ordinary conversation, making accidental activation likely. In a skill that can surface church event data, volunteer assignments, and liturgical planning context, unintended invocation could expose internal organizational information or cause the agent to enter a planning workflow when the user did not intend it.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill persistently stores volunteer names, phone numbers, availability, preferences, allergies, and inferred burnout data in a local JSON file, but provides no user-facing notice, consent flow, retention limits, or handling guidance for sensitive personal information. In this context, accidental collection or over-retention of church member data increases privacy risk and can lead to unauthorized exposure of personal or pastoral information.

Content

No source excerpt is available for this finding.

Scope Creep

Low
Category
Excessive Agency
Confidence
70% confidence
Finding

Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.

Content

Scanner excerpt · SKILL.md (reported line 14)May include surrounding context.

md
You are a church event planning assistant that helps ministry staff plan, organize, and execute events of all sizes. You manage the full lifecycle: from initial concept through post-event wrap-up, tracking tasks, timelines, vendors, volunteers, and logistics along the way.

You handle everything from weekly services to large-scale conferences. Your job is to reduce the mental load on church staff by keeping all the moving pieces organized and visible.

---

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The eval explicitly expects the skill to write to event-data.json as part of normal behavior, but it does not require any user confirmation or warning before performing that state-changing action. In an agent setting, silent file writes can create unintended persistence, overwrite prior data, or normalize modifying user data without informed consent, even if the content here is routine church event information.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
89% confidence
Finding

This markdown file specifies that the skill will write updated volunteer and task assignment data to event-data.json, which affects persisted user data. The description does not include any warning or disclosure that the skill will modify stored event records before or during execution.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The eval explicitly expects the skill to write to event-data.json without any mention of confirmation, visibility, or safeguards around modifying stored event data. In a church event-planning context this is a real, though low-severity, issue because silent state changes can cause incorrect schedules, vendor links, or tasks to be persisted without the user's awareness.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
87% confidence
Finding

The file explicitly expects the skill to update an event record in a data file, which is a user-data modification. The markdown does not include any warning or disclosure that running this skill will write changes to persisted data.

Content

No source excerpt is available for this finding.