T09 · Insecure Skill Coding Practices
- Location
README.md:43- Finding
Hardcoded ClawHub Access Token in Installation Documentation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent local semantic code-search helper, but its documentation exposes a credential-like ClawHub token and installs unpinned remote packages.
Review carefully before installing. Do not reuse the embedded ClawHub token; it should be revoked and replaced with user-provided authentication. Prefer installing a pinned, reviewed semgrepll version with hashes, and be aware that indexing code creates local cached embeddings of project content.
README.md:43Hardcoded ClawHub Access Token in Installation Documentation
clawhub.yaml:18Unpinned and Integrity-Unverified PyPI Dependency Installation
The README publishes a live-looking installation token directly in a command, which may enable unauthorized registry access, token abuse, or impersonated installs if the token is valid. In a skill distribution context, embedded credentials are especially dangerous because they are easy to scrape, reuse, and propagate into automated agent workflows.
The README makes a strong '100% offline capable' claim while also instructing users to install via a remote registry using a tokenized command. This is misleading security messaging: users may underestimate network exposure, trust boundaries, and supply-chain risk during installation, especially in an agent-skill context where remote installs can pull unreviewed content.
The trigger phrases are broad enough to match ordinary user requests about searching code or indexing a project, which can cause the skill to activate unexpectedly. In an agent setting, this increases the chance of unintended command execution against local project paths or repositories without clear user intent confirmation.
The trigger keyword 'semantic search' is broad enough to match many ordinary user requests that are not clearly intended to invoke this specific skill. Overbroad activation can cause unintended skill routing, which may run commands or influence responses in contexts where the user did not explicitly request this package.
The phrase 'search code by meaning' is ambiguous and conversational, so it may overlap with general programming help requests rather than explicit invocation of this skill. In an agent environment, ambiguous triggers increase the chance of accidental activation and unintended execution of indexing or search-related commands.
The trigger 'find code semantically' is similarly broad and could match common natural-language requests about understanding or locating code. Because this skill exposes command execution paths like indexing and searching local projects, loose activation boundaries raise the risk of unintended tool use on the wrong project or without clear user intent.