Back to skill

Security audit

Daycare Waitlist Status Board

Security checks for vulnerabilities and agentic risk

Overview

This is a prompt-only daycare waitlist organizer that avoids unnecessary child details and does not include code, network access, or persistence.

Reasonable to install if you want a structured daycare waitlist tracker. Avoid entering full child names, medical records, custody documents, home addresses, payment details, or identity documents unless you are keeping a private checklist, and verify licensing, fees, policies, and availability directly with providers or official regulators.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • YARA SignaturesMalware Match, Webshell Match, Cryptominer Match
  • 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 (6)

YARA rule 'agent_skill_prompt_injection_hidden_instructions': Prompt injection or hidden instructions embedded in AI agent skill text [agent_skills]

High
Category
YARA Match
Content
waitlist options without exposing private child details."
---
# Daycare Waitlist Status Board

## Purpose

Turn scattered childcare waitlist notes into a clear status board for comparing daycare, preschool, nursery, or early-childhood program options. The board helps the user track application status, follow-up timing, licensing checks, policy questions, availability signals, visit notes, and enrollment next steps.

This is a prompt-only family admin workflow. It is not childcare, legal, medical, licensing, safety, or parenting advice. The user must verify licensing status, policies, availability, costs, health requirements, and enrollment terms directly with official provider and regulator sources.

## Use This Skill When

Use this skill when the user needs to organize childcare waitlist logistics, especially when:

- They have applied to multiple daycare or preschool programs and need one comparison board.
- They need a follow-up cadence that is polite and not spammy.
- They want pro
Confidence
80% confidence
Finding
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).

Anti-Refusal Statement

High
Category
Anti-Refusal
Content
- Always tell the user to verify licensing, inspections, policies, staff ratios, fees, enrollment deadlines, and availability through official provider or regulator sources.
- Do not collect or expose unnecessary child details, medical records, custody documents, home addresses, payment information, or identity documents.
- Do not include private child details in shared artifacts; use initials, age range, or classroom category only when needed.
- Do not tell the user to misrepresent application details, pressure staff unfairly, skip required paperwork, or bypass safety policies.

## Example Prompts
Confidence
90% confidence
Finding
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.

Instruction Override

High
Category
Prompt Injection
Content
- Always tell the user to verify licensing, inspections, policies, staff ratios, fees, enrollment deadlines, and availability through official provider or regulator sources.
- Do not collect or expose unnecessary child details, medical records, custody documents, home addresses, payment information, or identity documents.
- Do not include private child details in shared artifacts; use initials, age range, or classroom category only when needed.
- Do not tell the user to misrepresent application details, pressure staff unfairly, skip required paperwork, or bypass safety policies.

## Example Prompts
Confidence
90% confidence
Finding
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.

Natural-Language Policy Violations

Medium
Confidence
96% confidence
Finding
The acceptance criteria explicitly require public-facing documentation to be English only. This is a natural-language locale restriction, and the file does not indicate that users may choose another language or that the restriction is justified by a region-specific compliance requirement.

Natural-Language Policy Violations

Low
Confidence
91% confidence
Finding
The language audit line treats English-only content as a required acceptance condition. This reinforces a language policy that excludes other locales without explaining why that limitation is necessary or offering user choice.

Natural-Language Policy Violations

Low
Confidence
96% confidence
Finding
The manifest sets "language": "en", which indicates a fixed language/locale constraint. Under the policy, locale restrictions should either provide user opt-in or be clearly justified as region-specific; no such justification appears in this file.

Static analysis

No suspicious patterns detected.