autonnel-skills
- Type
- Plugin
- Scanned
- Nov 13, 2026
- Version
- 9749eef7d6a2
- Files read
- 10
This plugin provides six Markdown skill guides that help an AI coding agent audit landing pages, design sales funnels, plan upsells and server-side tracking, compare platforms, and deploy the self-hosted Autonnel funnel builder. It contains no executable code of its own, and the main risks are minor hardening gaps in its deployment instructions, such as running an unpinned npm initializer package and passing an admin password on the command line where it can land in process lists, shell history, or chat logs.
What it can reach
- Other
- The plugin itself consists solely of Markdown skill guides and a JSON manifest, with no executable code, hooks, or background processes.
- Network
- When invoked, the skills guide the host agent to fetch user-supplied landing page URLs for audits, deploy to Cloudflare Workers, or call the user's own self-hosted Autonnel API.
- Shell commands
- When asked to launch a self-hosted funnel, the deployment skill provides Docker, Wrangler, and npm/pnpm CLI commands for the user or host agent to run.
Findings
-
LowAdmin password passed directly in command-line arguments
self-hosted-funnel-launch/SKILL.md:84
Although the launch skill warns against putting database or encryption secrets into commands, its admin CLI examples pass the administrator password as a plaintext command-line argument. If a user or agent runs this command on a shared server, the password is exposed to other local users in the system process list, saved in shell history, and recorded in the AI conversation transcript if executed through the agent.
Fix: Instruct the operator to create the initial admin account through the browser /setup wizard or run the command outside the AI chat using interactive input rather than a command-line argument.
-
LowUnpinned package and branch references in setup commands
self-hosted-funnel-launch/SKILL.md:136
While the Docker instructions pin an exact version tag, the Node source checkout section instructs running npm create autonnel@latest, which downloads and executes whatever version is currently tagged latest on npm without version pinning (and README.md similarly downloads docker-compose.yml from the mutable master branch). If the upstream package or branch were compromised, running the command would execute untrusted code at setup time.
Fix: Pin a specific verified version tag instead of @latest, or instruct cloning the repository at a specific release tag before installing dependencies.
