ClawHub
Back to skill

Security audit

Jiminny

Security checks for vulnerabilities and agentic risk

Overview

This skill coherently provides read-only access to a user-connected Jiminny account through the OOMOL oo CLI, with no bundled executable code or hidden persistence.

Install only if you want your agent to retrieve Jiminny account data through OOMOL. Treat transcripts, comments, coaching feedback, scorecards, and user lists as sensitive business data, and review any future version carefully if it adds actions tagged write or destructive.

SkillSpector

Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Description-Behavior Mismatch

Medium
Confidence
87% confidence
Finding
The manifest and description present the skill as only for 'searching and reading data,' but the body also documents support for state-changing actions. This mismatch can mislead an agent or reviewer into treating the skill as read-only, reducing scrutiny and increasing the chance that a future write-capable action is invoked without appropriate confirmation controls.

Intent-Code Divergence

Low
Confidence
81% confidence
Finding
The safety section says write/destructive actions will be tagged, but the action list contains no such tags while still asserting such actions exist. This creates an unreliable safety contract: users or agents may infer that all listed actions are safe reads, and future edits could introduce risky operations without clear labeling.

Vague Triggers

Medium
Confidence
89% confidence
Finding
The instruction to use this skill for 'ANY Jiminny request' is an overly broad trigger that can cause unintended invocation whenever Jiminny is mentioned, even when the user did not ask to use the connector. Over-broad routing increases the chance of unnecessary data access, privacy exposure, or incorrect tool selection in multi-tool environments.

Static analysis

No suspicious patterns detected.