ClawHub
Back to skill

Security audit

http-status-explainer

Security checks for vulnerabilities and agentic risk

Overview

This skill is a text-only helper for explaining HTTP status codes and does not request unusual access or perform sensitive actions.

Safe to install for HTTP debugging assistance. Do not paste API keys, cookies, Authorization headers, or other secrets into the assistant; the skill itself instructs the agent to avoid requesting or echoing them.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

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

md
5. For 429 with `Retry-After`, convert the wait to a human duration and advise
   respecting it instead of tight retry loops.
6. For 401 vs 403, distinguish "not authenticated" from "authenticated but not
   allowed" without asking the user to paste tokens.
7. For 502/503/504, suggest upstream health, timeouts, and recent deploys before
   rewriting business logic.
8. Never invent a vendor-specific root cause. Label guesses as hypotheses.

Static analysis

No suspicious patterns detected.