Back to skill

Security audit

Code Weather

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only skill that presents codebase health as a weather report and does not include code execution, credentials, persistence, or hidden data movement.

This skill appears safe to install as a lightweight markdown instruction set. Expect it to read or reason about repository health signals when invoked; review its output before acting on any suggested risk areas, especially before deploys or planning decisions.

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
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
80% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

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

md
Could destroy everything if it breaks. No warning.

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 30)May include surrounding context.

md
# Code Weather

> "You wouldn't go outside without checking the weather. Why would you start coding without checking the forecast?"

## What It Does

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The 'When to Invoke' section says to use the skill 'Every morning,' during standup, before deploys, and weekly, but it does not define a specific trigger phrase, command, or exclusion condition. This makes activation scope ambiguous and increases the chance of unintended invocation from general discussion about coding routines or team ceremonies.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.