The skill is vulnerable to prompt and command injection, allowing
Claims to do
Plan With Team: Create a detailed implementation plan based on the user's requirements provided through the `USER_PROMPT` variable. Analyze the request, think through the implementation approach, and save a comprehensive specification document to `.claude/.team-build/<name-of-plan>.md` that can be used as a blueprint for actual development work. Follow the `Instructions` and work through the `Workflow` to create the plan. Predefined agents are located under agents/*.md
Actually does
This skill analyzes user requirements from `USER_PROMPT` and optional orchestration guidance from `ORCHESTRATION_PROMPT`. It generates a detailed implementation plan in markdown format, saving it to `.claude/.create-feature/plans/<filename>.md`. The skill itself does not execute any `Task*` tools; it only describes their intended use within the generated plan.
The skill generates implementation plans that include instructions for deploying sub-agents using the `Task` tool. The `prompt` for these sub-agents is derived from user input (`USER_PROMPT`, `ORCHESTRATION_PROMPT`), allowing an attacker to inject malicious instructions into the sub-agents' prompts.
Task({ description: "...", prompt: "...", subagent_type: "general-purpose" })The generated plan includes a 'Validation Commands' section, which explicitly lists commands to be executed by other agents. User input can influence the content of these commands, creating a direct command injection vulnerability for downstream agents that execute the plan.
## Validation Commands Execute these commands to validate the task is complete and works end 2 end: - Example: `uv run python -m py_compile apps/*.py`
The skill writes the plan to `PLAN_OUTPUT_DIRECTORY/<filename>.md`, where the filename is generated based on the main topic of the plan (derived from user input). Insufficient sanitization of the filename could lead to overwriting critical files or creating files with unexpected extensions.
Save the complete implementation plan to `PLAN_OUTPUT_DIRECTORY/<descriptive-name>.md`
The plan format includes fields like 'External ticket subtask ID' and mentions creating subtasks in Jira, Linear, or GitHub. This implies potential interaction with external project management systems, which could be abused for social engineering (e.g., creating fake urgent tasks) or data exfiltration.
External ticket subtask ID <ID to the subtask in jira,linear or github for updating progress>
The agent identifies team members from `.claude/agents/team/*.md` files. If these agent definition files are compromised (e.g., via a supply chain attack), an attacker could poison the agent's knowledge base, leading to the deployment of malicious or altered sub-agents.
Identify from `.claude/agents/team/*.md` or use `general-purpose`.
[](https://mondoo.com/ai-agent-security/skills/github/Fleron/Claude-plugins/team-plan)<a href="https://mondoo.com/ai-agent-security/skills/github/Fleron/Claude-plugins/team-plan"><img src="https://mondoo.com/ai-agent-security/api/badge/github/Fleron/Claude-plugins/team-plan.svg" alt="Mondoo Skill Check" /></a>https://mondoo.com/ai-agent-security/api/badge/github/Fleron/Claude-plugins/team-plan.svgSkills can read files, run commands, and access credentials. Mondoo helps organizations manage the security risks of AI agent skills across their entire fleet.