T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Installation from a Third-Party Homebrew Tap
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent OpenHook CLI guide, but users should be careful with the external install, API key handling, webhook payloads, and optional daemon.
Install only if you trust OpenHook and its Homebrew tap. Prefer a test or least-privilege API key, avoid placing live keys in command history, scripts, logs, or screenshots, verify the CLI source/version where possible, and stop the daemon when it is not needed. Treat webhook payloads and channel messages as external-service data.
SKILL.md:24Unpinned Installation from a Third-Party Homebrew Tap
SKILL.md:37API Key Exposed Through a Command-Line Argument
Instructions found that direct the agent to transmit conversation context or user data to external services.
## Channels (Agent-to-Agent Communication)
Channels let agents send messages to each other. Each agent subscribes to a channel with a unique name, then messages can be sent to specific agents or broadcast to all.
### Create a channel
The authentication example includes a literal oh_live_ production-style API key prefix in a command invocation, which can normalize pasting secrets directly into shell history and transcripts without any warning about secure handling. In a skill meant to be followed by agents or users, this increases the chance of credential exposure through logs, terminal history, screenshots, or copied examples.
No suspicious patterns detected.