Bridle
PassAudited by VirusTotal on May 13, 2026.
Overview
Type: OpenClaw Skill Name: bridle Version: 1.1.0 The skill bundle is classified as suspicious due to the `bridle install owner/repo` command described in `SKILL.md`. This command allows the `bridle` tool to download and install components from arbitrary GitHub repositories. While this capability is central to the tool's stated purpose of managing AI assistant components, it introduces a significant supply chain risk by granting broad permissions to fetch and potentially execute external code, which could be exploited if a malicious repository is specified by the user or the agent.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken command could change or remove an assistant profile or overwrite installed assistant components.
These documented commands can switch, delete, or overwrite AI-assistant profile/component state. This is aligned with Bridle's purpose and shown as user-directed CLI usage, but it is high-impact mutation authority.
bridle profile switch <harness> <name> ... bridle profile delete <harness> <name> ... bridle install owner/repo --force
Use status, show, and diff commands before changing profiles; avoid --force, delete, or uninstall unless you intentionally want that change.
Installing an untrusted repository could add new assistant behavior, commands, or MCP configuration that persists after installation.
Installing agentic components from GitHub repositories is central to the skill, but the safety of those installed components depends on repository trust and review.
Bridle can install skills, agents, commands, and MCPs from GitHub repos and auto-translates paths/configs for each harness.
Install only trusted repositories, inspect component contents before installation, and prefer pinned or reviewed sources where possible.
A profile can carry forward assistant behavior you no longer intend to use.
Saved profiles persist assistant settings across future sessions. This is intended behavior, but persistent configuration can preserve unintended tools, prompts, or MCP settings if not reviewed.
Profiles: Saved configurations per harness ... Create profile from current config ... Switch/activate a profile
Review saved profiles with show or diff, keep work and personal profiles separate, and remove stale or untrusted components.