ClawHub
Back to skill

Security audit

Agent Team Orchestration 1.0.0

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-only orchestration skill whose agent spawning, shared files, reviews, and scheduled workflow examples match its stated purpose.

Before installing, treat this as a process template: define exact schedules, timezones, agent permissions, shared directory boundaries, and approval rules before using it to run real multi-agent workflows.

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
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Vague Triggers

Low
Confidence
89% confidence
Finding
The schedule description 'Every morning' is ambiguous because it does not define a concrete activation time, timezone, or execution window. In a patterns document, this can lead to inconsistent or unintended task invocation across teams or environments.

Vague Triggers

Low
Confidence
91% confidence
Finding
The phrase 'Every few hours (or on trigger)' is too vague because it leaves both the periodic cadence and the event trigger undefined. This can cause accidental over-invocation or inconsistent behavior when different operators interpret the trigger differently.

Vague Triggers

Low
Confidence
90% confidence
Finding
The term 'Periodic' does not specify when or how often the pattern should run, making the activation condition unclear. Without explicit scope or negative examples, implementations may run too often, too rarely, or under the wrong conditions.

Static analysis

No suspicious patterns detected.