T01 · Skill Instruction Hijacking
- Location
SKILL.md:143- Finding
Mandatory Global Agent Behavior and Output Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is mostly a persona and orchestration skill, but it asks agents to act too broadly and automatically, including suppressing clarification and touching persistent or financial-like state.
Install only if you are comfortable with a broad multi-agent persona pack and can enforce host-side controls. Require confirmation before deployments, external posting, tool expansion, sub-agent spawning, memory access, or Shannon mint/debt changes; avoid using the bundled dashboard on a sensitive origin; and treat the prototype and analytics guidance as needing privacy review and pinned tooling.
SKILL.md:143Mandatory Global Agent Behavior and Output Hijacking
SKILL.md:123Excessive Meta-Orchestrator Permissions and Cross-Session Capabilities
autoresearch-fiesta-agents/dashboard.html:102DOM-Based Cross-Site Scripting Through Unescaped Dashboard Data
autoresearch-fiesta-agents/dashboard.html:7Third-Party JavaScript Loaded Without Subresource Integrity
The skill defines authority to mint internal currency via a network endpoint and explicitly supports negative-balance debt operations, which extends the agent from task orchestration into financial state manipulation. Even if framed as fictional 'Shannon' accounting, this creates a dangerous pattern where an agent may be induced to perform unauthorized economic actions, trigger local network requests, or normalize budget/debt decisions without user approval.
The README instructs users to invoke a central orchestrator for a vague, open-ended task ('execute a complete redesign of our landing page') without any stated scope limits, approval boundaries, or department restrictions. In a multi-agent skill, this can encourage unconstrained delegation and broaden the blast radius of mistakes, causing excessive actions, unintended coordination, or use beyond the user's minimally necessary intent.
The skill mandates a fixed English introduction for every response with no user control, which can override user preferences, localization needs, accessibility requirements, or upstream system prompts. In an agent framework, hard-coded response prefixes also create prompt rigidity that can interfere with policy-compliant behavior and make downstream automation depend on non-optional text.
The output schema hard-codes an English-only first line and fixed section order for all responses, forcing behavior regardless of context. This can break multilingual use, accessibility accommodations, or system-required formats, and can cause agents to prioritize template compliance over safer or more appropriate interaction patterns.
The manifest description "Certification specialist" is extremely broad and does not define specific trigger phrases, contexts, or limits for when this skill should be used. In a markdown/manifest-scoped review, this creates ambiguity about activation and increases the risk of unintended invocation for generic certification-related requests.
The line "I will help you" is a highly generic assistance phrase that overlaps with common everyday language and provides no domain-specific trigger constraints. This makes the skill's invocation boundaries unclear and can contribute to accidental or overly broad activation.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
---
name: brand-strategist
description: "Brand identity specialist — positioning, voice and tone, visual identity systems, brand guidelines"
version: 1.0.0
department: design
color: gold
---
# Brand Strategist
## Identity
- **Role**: Brand identity architect and consistency guardian
- **Personality**: Strategic, story-driven, fiercely protective of brand coherence. Knows that brand is what people say when you're not in the room.
- **Memory**: Recalls brand pivots that worked, consistency failures that eroded trust, and positioning wins
- **Experience**: Has built brands from zero and rescued brands that lost their way
## Core Mission
### Define Brand Strategy
- Brand positioning and differentiation in the competitive landscape
- Mission, vision, and values that are actionable (not wall art)
- Target audience definition with psychographic depth
- Brand personality and archetype selection
- Competitive positioning
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Test and iterate — first generation is a starting point
### Ethical Use
- No generating real people's likenesses without consent
- Disclose AI-generated content when required by context
- Respect artist styles without mimicking specific living artists by name
- Be aware of bias in training data and actively counter it
The skill explicitly recommends collecting user emails and using session recording for feedback without mentioning consent, privacy notice, retention, or lawful handling of personal data. In context, this is more dangerous because the skill targets MVP builders who may deploy quickly and expose real users to tracking and data collection practices that violate privacy expectations or regulations.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
Using npx supabase init without pinning an exact CLI version can cause users to execute whatever current package version is served at runtime, increasing supply-chain and reproducibility risk. In a rapid-prototyping skill that encourages speed over hardening, users are more likely to run the command uncritically, which makes the guidance more dangerous in practice.
Using npx supabase start without an exact pinned version has the same supply-chain and non-reproducibility issue as the prior command: the invoked CLI version may change over time or be replaced by a compromised upstream package. Because the skill is explicitly optimized for fast execution, it normalizes skipping verification steps and increases the chance this guidance will be followed as-is.
The manifest description "Licensing specialist" is a generic role label rather than a specific invocation condition or narrowly scoped trigger. In a manifest file, this broad phrasing can overlap with many ordinary licensing-related requests and does not provide exclusions or negative examples to limit when the skill should activate.
The skill description "Licensing specialist" is broad enough that an orchestrator or user could invoke it for a wide range of loosely related licensing requests without clear boundaries, increasing the chance of unintended activation or overreach. In this file there is no malicious payload, but the weak scoping can still cause unsafe or inappropriate task routing in multi-agent systems.
The manifest description "Marketing specialist" is too generic and overlaps with common requests, making it unclear when this skill should activate versus other marketing-related skills. The file provides no explicit trigger phrases, scope boundaries, or exclusion conditions to narrow invocation.
The description "Marketing specialist" is very generic and does not define when this skill should be invoked versus other marketing-related skills. Without narrower scope, constraints, or negative examples, the activation condition is ambiguous and risks unintended invocation.
The skill description is overly generic ('Marketing specialist') and does not define clear activation boundaries, allowed actions, or prohibited tasks. In a multi-agent environment, this can cause the agent to be invoked for loosely related requests and increase the chance of scope creep, prompt misuse, or inappropriate handling of tasks better suited to other more constrained agents.
The skill description 'Marketing specialist' is so broad that it provides little constraint on when the agent should be invoked or what tasks are in scope. In a multi-agent system, this can cause over-selection or misuse for adjacent tasks, increasing the chance of prompt injection exposure, unsafe delegation, or inappropriate access to marketing-adjacent workflows.
The description "Marketing specialist" is generic and does not define when this skill should activate versus when other marketing-related skills should not. Because the file provides no specific trigger phrases, scope limits, or exclusion examples, it creates ambiguity that could cause unintended invocation.
The manifest description is simply "Marketing specialist," which is an extremely broad label that could match many ordinary requests and does not clarify when this skill should or should not be invoked. The file also provides no explicit trigger phrases, scope boundaries, or exclusion examples to limit activation.
The manifest description is generic ('Marketing specialist') while the skill is named 'twitter-specialist', which can cause the agent-selection system to invoke this skill for broad marketing tasks unrelated to Twitter. That scope ambiguity increases the chance of unintended activation, cross-domain overreach, and incorrect handling of requests that should route to a more specific or differently governed skill.
The skill description and body define a broadly empowered 'operations specialist' and 'compliance officer' without clear activation boundaries, allowed actions, or prohibited tasks. In an agent system, this ambiguity can cause the agent to be invoked for sensitive compliance, monitoring, reporting, or policy interpretation tasks beyond its safe scope, increasing the risk of overreach, unsafe automation, or trust abuse.
The manifest description "Operations specialist" is so generic that routing logic may invoke this skill for a wide range of unrelated operational or analytical requests. Overly broad matching can cause unintended skill activation, which increases the chance of inappropriate access to task context, incorrect automation, or delegation to the wrong agent.
The manifest description "Operations specialist" is very broad and non-specific, which increases the chance that routing or invocation systems will select this skill for generic operational, reporting, or administrative requests beyond its intended scope. Overly broad matching can cause inappropriate tool/skill activation, expanding the attack surface for prompt-injection, data exposure, or unintended authority in multi-agent environments.
The description "Operations specialist" is overly generic and overlaps with many common operational or finance-related requests, which can cause the skill to be invoked unintentionally. Over-broad routing increases the chance that a user task is handled by the wrong agent, leading to inappropriate access to operational context, inaccurate outputs, or bypass of more specialized controls.