Back to skill

Security audit

13-Day Sprint Method - Productivity System

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only productivity guidance skill with no executable code, credentials, persistence, or hidden data access.

This skill appears safe to install for productivity coaching. Treat its calendar method as advisory, and keep any cleanup, release, or project-management actions under your own control.

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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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 (2)

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
80% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

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

md
Depending on the tone, provide specific guidance:

- **Tone 1 (Magnetic):** Help user define a clear, achievable goal for the 13-day sprint
- **Tone 2 (Lunar):** Encourage acknowledging doubts without judgment
- **Tone 3 (Electric):** Motivate taking immediate action, even small steps
- **Tone 4 (Self-Existing):** Help structure and document the plan
- **Tone 5 (Overtone):** Encourage sharing progress with others

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The instructions and tone system consistently define Tone 1 as the start of a sprint, and the calendar shows Sprint 4 starts on 2026-02-09 with Tone 10 only because the sprint numbering is continuous from a prior offset. The example tells users 'the next sprint (Sprint 4) begins on February 9 with Tone 10' while also saying the ideal goal-setting day is February 13 (Tone 1), which actively conflicts with the method's stated sprint-start semantics and could mislead users about how to use the system.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.