Security audit
Security checks for vulnerabilities and agentic risk
This is a disclosed workflow-management plugin that stores local workflow state and guides agents through planning, execution, review, and delivery without evidence of hidden network access, credential use, or destructive behavior.
Install this when you want structured, persistent agent workflows. Review the local storage location because workflow names, notes, and outputs may persist across sessions, and keep an eye on broad process skills like verification or debugging if you prefer lightweight handling for small tasks.
The skill text expands its process to 'every task', which conflicts with the manifest's narrow trigger condition for brainstorming-only use. This creates instruction-scope drift: if selected, the skill can inappropriately force design-first behavior onto routine or execution-oriented requests, potentially blocking intended workflows and causing the agent to ignore user intent.
The hard gate prohibits execution or deliverables before design approval, but nearby instructions require exploring project context and later mandate task creation and ordered completion. This contradiction can lead the agent to interpret pre-approval file inspection or task persistence as allowed despite the gate, weakening safety boundaries and making behavior unpredictable.
The instruction to create a task for each checklist item suggests persistent session/task-state creation for every brainstorming engagement. Unnecessary persistence can expose user intent, internal planning, or sensitive project metadata across session boundaries or to other skills/tools, especially when persistence is automatic rather than user-approved.
## Checklist
You MUST create a task for each of these items and complete them in order:
1. **Explore project context** — check existing files, docs, prior work
2. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
The skill contains contradictory cleanup guidance: earlier text says Option 2 keeps the working copy until review is complete, but the later 'Always' section says to clean up for Options 1 and 4 only. This inconsistency can cause the agent to either skip intended cleanup or clean up at the wrong time, increasing the chance of accidental data retention or premature deletion.
The manifest narrowly limits this skill to concrete, reproducible debugging, but the body expands applicability to 'ANY unexpected situation,' which can cause the agent to invoke a rigid debugging workflow in contexts outside its approved scope. This kind of scope drift is dangerous because it can override higher-level routing expectations, leading to misapplication, delayed responses, and inappropriate behavior on non-debugging tasks.
The skill instructs use even when issues seem simple or urgent, which undermines the manifest's exclusions against straightforward one-step tasks and situations where the user wants immediate simple fixes. In an agentic system, this can bias the model toward unnecessarily invoking a heavyweight troubleshooting process, causing denial-of-service-by-friction, user frustration, and reduced compliance with intended tool-routing constraints.
The manifest description uses very broad trigger language such as "before wrapping up any task" and "delivering results," which can cause the skill to activate in many ordinary contexts. Over-broad activation can coerce agent behavior, inject procedural constraints into unrelated tasks, and increase the chance that higher-priority workflows are interrupted or steered unexpectedly.
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
| **Refactor** | Close loopholes while maintaining compliance |
| **Write test first** | Run baseline scenario BEFORE writing skill |
| **Watch it fail** | Document exact rationalizations agent uses |
| **Minimal code** | Write skill addressing those specific violations |
| **Watch it pass** | Verify agent now complies |
| **Refactor cycle** | Find new rationalizations → plug → re-verify |
Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
1. **Find new rationalizations** — Run variations of the pressure scenario
2. **Document new violations** — Add to Red Flags section
3. **Plug loopholes** — Update skill, re-verify
4. **Repeat** until no new violations found in 3 consecutive runs
## Skill Structure
No suspicious patterns detected.