T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:43- Finding
Mutable Remote Installer Is Executed Directly Through a Shell
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it needs Review because it can install tools, use an authenticated X session, post publicly after approval, create agent files, and store detailed personal/social data indefinitely.
Install only if you are comfortable with an agent using your authenticated X account, running command-line tools, and keeping a local plaintext profile of your identity, voice, real replies, audience, leads, and performance history. Review or remove the automatic curl-to-sh install path, pin dependencies, approve every post/reply, restrict when the skill can activate, and periodically inspect/delete the generated memory and strategy files.
SKILL.md:43Mutable Remote Installer Is Executed Directly Through a Shell
README.md:29Installation Instructions Execute Unpinned Third-Party Packages
SKILL.md:379Externally Sourced Post Text Is Interpolated into Shell Commands
SKILL.md:298Arbitrary Media URLs Are Retrieved Without Protocol, Destination, or Size Restrictions
SKILL.md:600Personal and Behavioral Data Is Retained Indefinitely in Plaintext
The skill explicitly states that it 'self-updates its own strategy files based on what's working,' which is a self-modification capability. In the context of an instruction-following agent, self-modifying memory and strategy artifacts can drift into unsafe behavior, preserve poisoned data, or broaden future actions without the user noticing.
- **Writes replies** in your authentic voice (not AI-sounding generic praise)
- **Runs engagement sessions** with Reply Cards for your approval before posting
- **Plans content** with a 60/40 engagement-to-showcase ratio
- **Tracks performance** and self-updates its own strategy files based on what's working
- **Manages DM outreach** for client acquisition, job hunting, or networking
- **Operates the CLI** — can post, reply, search, and analyze directly via `twitter-cli`
The skill instructs the agent to install and bootstrap host-side tooling (twitter-cli and potentially uv) including piping a remote script directly into sh. That exceeds the normal scope of a social media drafting skill and creates a supply-chain and host-modification risk, especially because it runs based on skill logic rather than an explicit, separate user consent flow.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[populated during onboarding]_
<!--
The agent should write a thorough analysis covering:
1. **The Context Economy in [User's Niche]**
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[populated during onboarding -- one sentence that captures the user's brand]_
<!--
Format: "I help [target audience] achieve [outcome] through [unique method/skill]."
Example: "I build cinematic landing pages that make startups unforgettable."
Example: "I help SaaS founders ship faster with AI-directed full-stack development."
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[populated during onboarding]_
<!--
| Competitor | Their Angle | Their Weakness | Our Opportunity |
|-----------|-------------|----------------|-----------------|
| @handle1 | [what they do] | [what they miss] | [how we fill the gap] |
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[posts are added here by the Content Planner workflow and removed/marked as posted after execution]_
<!--
### Planned Post #N
- **Status:** draft / approved / posted / skipped
- **Type:** [post type from content pillars]
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[populated during onboarding -- the agent analyzes the user's current X presence and identifies what's broken. Example structure:]_
<!--
You have a **[type] problem**, not a [type] problem. Your [evidence of skill] confirms this -- [specific proof]. Yet your X presence doesn't reflect any of it.
**Things that are broken right now:**
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[populated during onboarding -- customized to the user's primary goal]_
<!--
For CLIENT ACQUISITION:
- Warm DM system
- Video audit lead magnet
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
_[populated during onboarding -- realistic targets based on current follower count, time budget, and niche competitiveness]_
<!--
| Metric | Day 30 | Day 60 | Day 90 |
|--------|--------|--------|--------|
| Followers | [target] | [target] | [target] |
The hidden HTML comment contains operational instructions that are not visible in normal rendered Markdown, directing the agent to analyze the user's real replies and mandatorily read other files before producing output. Hidden instructions are dangerous because they can silently steer model behavior, expand collection of personal data, and create unreviewable control paths that the user may not see or consent to.
## Voice & Reply Architecture
<!-- Auto-populated during onboarding by analyzing the user's real replies. MANDATORY READ before writing ANY reply. Also read voice-anti-patterns.md EVERY TIME. -->
### Vocabulary Fingerprint
This workflow includes multiple automatic writes across memory and strategy files with no explicit approval checkpoint. Because those files influence future agent behavior, automatic persistence of externally sourced analysis creates a high-risk prompt/data poisoning pathway and can silently alter project state beyond what a user expects from a social media assistant.
The README advertises automatic X account research and browser-session-based authentication but does not prominently warn that the skill may access account data through an active browser session. In this context, the skill can inspect personal or business social activity and act with authenticated context, so missing privacy and data-access disclosures are security-relevant.
The README describes a self-evolving system that populates and updates multiple strategy, profile, and memory files, but it does not clearly warn users about persistent file writes and ongoing self-modification. In an agent skill, silent long-lived memory writes can expose sensitive business data, entrench bad instructions, or create difficult-to-audit behavior changes over time.
The README presents the skill as a social media manager, but the described behavior includes installing external tooling, using browser-backed account access, operating a CLI, and conducting account research. That broader operational scope materially expands the trust boundary and attack surface beyond content drafting.
The documentation mixes claims that the skill can 'post, reply, search, and analyze directly' with a later assurance that it never posts without explicit approval. This inconsistency can mislead users about the actual autonomy of the skill and increase the chance of unintended account actions.
The README instructs users to execute npx skills add ... without pinning a specific version of the installer. That creates a supply-chain risk because the fetched package version can change over time, and users may execute unreviewed code during installation.
The trigger list includes very broad terms such as "post," "content," "engagement," "growth," "brand," and "DM outreach," which can match many unrelated requests. Over-broad activation increases the chance that this powerful skill is invoked in the wrong context, exposing stored data or causing unintended actions like CLI use or posting workflows.
The skill states it will automatically research the user's X account and populate strategy files, collecting profile, engagement, and behavioral data without an upfront privacy notice or consent checkpoint. Because the system also persists this data, the missing disclosure materially increases privacy risk.
The skill promotes an evolving memory system that automatically researches the user's account and stores personal strategy data across files. Persistent retention and propagation of identity, behavioral, and writing-style data increases privacy exposure and the blast radius of any later misuse or compromise.
The setup instructions describe automatic installation using shell commands, including fetching and executing a remote install script, without a prominent safety warning or explicit user approval. This encourages risky execution behavior on the host and normalizes unsafe setup practices.
The skill instructs the agent to archive the user's real replies word-for-word in a reference file. Exact archival of authentic communications creates a reusable corpus of personal expression that can expose sensitive information, enable impersonation, and expand harm if the files are leaked or reused out of context.
The skill directs the agent to detect its host environment and create IDE/CLI-specific sub-agents, files, or configs. This is an unnecessary expansion of privileges for an X/Twitter manager and can mutate the local workspace or agent runtime in ways the user did not clearly request.
The session initialization requires reading all stored profile, memory, and reply-archive files before any workflow. This broad mandatory reuse of previously collected data increases unnecessary exposure of personal information and makes unrelated tasks depend on maximum-context retrieval.
The memory system directs indefinite accumulation of detailed interaction history, audience intelligence, leads, follower traits, and behavioral analytics. Long-lived, ever-growing storage without retention limits or purpose boundaries materially raises privacy, profiling, and secondary-use risks.
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.
- Invent flags not listed in this document
- Use `--video` flag (doesn't exist -- video uses `--image` flag with .mp4)
- Post without verifying character count
- Chain multiple `twitter` commands with `&&` without checking each one succeeded
- Use single quotes for text arguments
## Fetching Data
Detected: suspicious.prompt_injection_instructions