Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
frigatebird
v1.0.0Use the frigatebird npm package to interact with X from the CLI with bird-style command parity, posting/reply/article support, and list automation without X API keys.
⭐ 0· 990·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description match the SKILL.md: this is a Playwright-based CLI that operates against X using browser session cookies rather than API keys. Asking for cookie/profile inputs is consistent with that goal. However, the skill metadata declares no config paths or credentials while the runtime instructions explicitly reference cookie and browser-profile options (e.g., --cookie-source, --chrome-profile, --ct0), so there is a transparency gap about required local access.
Instruction Scope
SKILL.md instructs installing/using the third‑party npm package (npm install -g frigatebird / npx frigatebird) and documents flags that imply reading browser cookies, profile directories, or session tokens. Although it doesn't contain explicit steps like "read ~/.config/..." the presence of --chrome-profile/--cookie-source/--ct0 flags strongly implies access to sensitive local data (cookies/session tokens). The instructions do not limit or explain how those secrets are handled, nor do they declare that you must supply or allow access to them.
Install Mechanism
There is no install spec baked into the skill (instruction-only), which lowers direct platform risk. But the SKILL.md tells users/agents to install an npm package whose source/homepage is absent from the metadata. Installing an unreviewed npm package (global or via npx) can execute arbitrary code on the host. The absence of a repository/homepage or vendored code means the package cannot be audited from this skill bundle.
Credentials
The skill declares no required env vars or config paths, yet documents flags for sensitive tokens and cookie/profile sources (e.g., --auth-token, --ct0, --cookie-source, --chrome-profile). These are highly sensitive (session cookies/tokens) and the skill does not declare that access in metadata nor describe safe handling. That mismatch means users may not realize what credentials or local files are needed or at risk.
Persistence & Privilege
The skill does not request elevated platform privileges, does not set always:true, and does not include an install script in the bundle. It doesn't ask to modify other skills or agent settings. However, because it encourages installing an external npm package, that package could request persistence at install/runtime (outside the scope of this bundle).
What to consider before installing
This skill describes a legitimate-sounding use (controlling X via browser cookies instead of API keys), but it has transparency and provenance gaps. Before installing or running anything: 1) Do not run npm install -g frigatebird or npx frigatebird unless you trust the package source—no homepage or repo is provided here. 2) Understand that operation requires session cookies or browser profiles (ct0, cookie files, chrome/firefox profiles). Those are equivalent to account credentials—sharing them or pointing a tool at them can give full account access. 3) If you must use this flow, prefer to run the CLI in a sandboxed environment or inspect the package source code first (look up the npm package, repository, and recent maintainers). 4) Ask the skill author to declare required config paths/credentials in metadata and to provide a repository/homepage and security/privacy notes about how session tokens/cookies are read, stored, and transmitted. Without those, treat installation as risky.Like a lobster shell, security has layers — review code before you run it.
latestvk97ernw822cxg9q0xa7xcpc4h980tka0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.