Back to skill

Security audit

Ministry Weekly

Security checks for vulnerabilities and agentic risk

Overview

This instruction-only church content skill is clearly scoped to weekly ministry communications, with disclosed local storage and confirmation-gated Telegram posting.

Before installing, users should be comfortable with a local ministry-data.json file storing church profile and weekly planning history. Do not put congregant PII, giving records, attendance lists, or identifiable prayer requests into the workflow. Only configure Telegram if you want the assistant to offer confirmed posting through your own Telegram integration.

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
  • 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 (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The README explicitly says the skill responds to casual phrasing like 'help me with Sunday's stuff' or 'I need content for this week' in a church context, which broadens activation beyond tightly scoped weekly-production commands. In a conversational assistant environment, this can cause unintended skill activation during ordinary church-related discussion, leading to unexpected persistence of church data or generation/posting workflows the user did not intend to invoke.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.