ClawHub
Back to skill

Security audit

rez-package-authoring

Security checks for vulnerabilities and agentic risk

Overview

This skill is a Rez package-authoring guide whose build and release instructions are disclosed and aligned with its purpose.

Install this skill only if you want Codex to help author or review Rez package.py files. Be aware that following its release workflow can install local Rez packages or run rez-release, so review those actions before publishing to shared package repositories.

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

md
1. Read the existing `package.py` and `rez-build --view-pre` output before editing anything.
2. Classify the requested change against decision 1 — version or variant — before touching
   `requires`.
3. Widen or narrow each range deliberately; never copy a range from another package without checking
   it means the same thing.
4. Prefer `~` and `!` over hard requirements when you are constraining rather than requiring.
5. Validate with `rez-build --view-pre`, then `rez-build --install`, then `rez-env` in a separate

Static analysis

No suspicious patterns detected.