T01 · Skill Instruction Hijacking
- Location
references/slide-structure.md:61- Finding
Mandatory Promotional Content and Lead-Generation Links in Audit Output
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent for a branded SEO/GEO audit, but it directs public publishing of client audit material without a clear consent or review gate.
Install only if you are comfortable with a Psyke-branded workflow that may crawl websites, use external AI/search tools, create a public GitHub repository, and deploy the audit publicly to Vercel. Before use, require explicit client approval, review staged files, prefer private/access-controlled publishing, and pin deployment tooling.
references/slide-structure.md:61Mandatory Promotional Content and Lead-Generation Links in Audit Output
SKILL.md:185Unpinned Remote Package Execution Through npx
SKILL.md:184Forced Public Repository Can Disclose Client Audit Data
The skill directs public GitHub publication and Vercel deployment without an explicit warning or consent step, which is especially dangerous because the generated artifact may include client names, URLs, audit findings, and competitive analysis. In this business context, that can leak sensitive commercial information and reputationally damaging security or SEO weaknesses.
The trigger phrases are broad enough to match routine requests like 'run an audit' or 'audit this site', increasing the chance that the skill activates unintentionally. Because the skill performs external fetching, benchmarking, and publication steps, accidental invocation can lead to unapproved data collection and disclosure.
The skill instructs creating a public GitHub repository for each audit, which can expose client audit content, site findings, competitor data, and potentially sensitive business intelligence to the public internet. This exceeds the core task of generating an audit deck and creates an unnecessary data disclosure path.
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.
Deploying the generated audit to Vercel publishes client-facing content to an external service, potentially making confidential findings accessible via a public URL. In the context of SEO/GEO audits, the deck may contain weaknesses, benchmarks, and internal recommendations that should not be exposed without informed consent.
The instructions require including queries with "Australia" and Australia-specific location examples, which imposes a locale constraint in the workflow. The document does not offer a user choice of region or explain that the framework is intended only for Australian clients, so this is a natural-language locale policy issue.
No suspicious patterns detected.