Security audit
Security checks for vulnerabilities and agentic risk
This skill is meant for external technical knowledge lookup, but it asks for broad file and command permissions and may send user context to an outside service without enough scoping guidance.
Review this before installing if you work with private code, credentials, customer data, or internal systems. Use it only for public technical-reference lookups, avoid sending secrets or proprietary snippets, do not expose the knowledge token in logs or terminal output, and restrict write/exec behavior unless it is explicitly user-directed and narrowly bounded.
The skill presents itself as a narrow external knowledge retrieval tool, but its declared tool permissions include read, write, exec, glob, and grep. This mismatch can cause an agent or user to invoke the skill with a lower perceived risk than warranted, enabling unnecessary filesystem access or command execution beyond the documented purpose.
The documentation claims the tool is stateless and does not store results, but later sections describe file reading, writing, and file-processing behaviors. This inconsistency can mislead operators into assuming no local persistence occurs, when the available capabilities could write sensitive retrieved data to disk or otherwise retain it.
The security section says only allowlisted safe commands should be run and user input must not be concatenated into commands, but the skill elsewhere advertises general command execution. That contradiction weakens operator expectations and increases the chance that downstream implementations will expose command injection or unsafe shell usage under the guise of normal skill behavior.
The invocation guidance is overly broad, suggesting use whenever coding, debugging, deployment, or similar technical work occurs. Broad triggers increase the chance that sensitive prompts, code, configuration, or secrets are sent to an external service unnecessarily, and can also cause the skill to be selected in situations where its high-risk capabilities are not needed.
The examples encourage triggering external queries whenever the agent perceives a generic knowledge gap or uncertainty. This ambiguity can cause excessive externalization of user prompts and context, including sensitive or proprietary material, without a clear necessity or user awareness.
The skill description explains that the agent can query an external knowledge service, but it does not provide a clear, prominent warning that user prompts or embedded context may be transmitted to a third-party endpoint. Without explicit disclosure, users may unknowingly expose sensitive data, code, credentials, or business information to an external service.
No suspicious patterns detected.
