ClawHub
Back to skill

Security audit

Bayesian Reasoning

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only Bayesian reasoning guide with examples; its main issue is a broad activation trigger that may cause irrelevant use, not unsafe behavior.

Use this as a reasoning aid, especially when interpreting evidence or base rates. For medical, legal, financial, security, or hiring decisions, verify inputs and thresholds with appropriate experts or data sources, and be aware the broad "update" trigger may activate the skill when ordinary conversation was intended.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (2)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
75% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 22)May include surrounding context.

md
- "Evidence is consistent with X" is being treated as proof of X
- Base rates ignored — a rare event treated as probable because evidence "looks like" it
- Correlated evidence pieces treated as independent updates
- A benchmark score, AI-capability claim, AI-adoption stat, or AI-capex/valuation figure is being treated as proof without asking how often that signal appears when the underlying claim is false
- Someone says "Bayesian," "prior," "posterior," "base rate," "likelihood ratio," "update"

**Not when:** genuinely deterministic; no data to anchor a prior; cost of formal update exceeds the value of being more right.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger list includes the standalone term 'update', which is a very common conversational word and can cause this skill to activate in many contexts unrelated to Bayesian reasoning. Over-broad activation can steer conversations into probabilistic framing when not intended, creating prompt-routing errors and reducing reliability, though it does not directly enable code execution or privilege escalation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.