omc-setup

Pass

Audited by Gen Agent Trust Hub on Nov 8, 2026

Risk Level: SAFECOMMAND_EXECUTIONEXTERNAL_DOWNLOADSPERSISTENCEINDIRECT_PROMPT_INJECTION
Full Analysis
  • [COMMAND_EXECUTION]: The skill executes multiple bash and node scripts bundled with the plugin to handle the configuration lifecycle. Specifically:
  • Invokes setup-claude-md.sh and setup-progress.sh from the plugin root to manage CLAUDE.md and state tracking.
  • Uses node to probe configuration states and repair plugin cache references.
  • Uses jq extensively to safely read and mutate JSON configuration files.
  • [EXTERNAL_DOWNLOADS]: The skill facilitates the installation of the 'oh-my-claude-sisyphus' global CLI tool and checks for updates using well-known services:
  • Performs npm install -g for the project's own CLI tool after prompting the user.
  • Uses npm view to check for the latest versions on the official registry.
  • Interacts with the GitHub API via the gh CLI to star the project repository, contingent on user authentication and consent.
  • [PERSISTENCE]: The skill establishes persistence for its environment by:
  • Modifying global and project-local CLAUDE.md files to inject managed imports and OMC markers.
  • Updating ~/.claude/settings.json to enable experimental features (Agent Teams) and configure display modes.
  • Modifying .git/info/exclude to manage project-specific file ignore rules.
  • [INDIRECT_PROMPT_INJECTION]: The skill possesses an attack surface for indirect prompt injection due to its interaction with external data:
  • Ingestion points: Reads and parses settings.json, .omc-config.json, and .omc/state/setup-state.json during the setup and resume phases.
  • Boundary markers: Does not utilize explicit boundary markers or 'ignore' instructions for the data read from these files.
  • Capability inventory: Possesses capabilities for shell execution (bash), package management (npm), and local file modification across all phases.
  • Sanitization: Employs jq for JSON manipulation, which provides structural validation and prevents syntax-level corruption, though it does not sanitize the semantic content of the instructions.
Audit Metadata
Risk Level
SAFE
Analyzed
Nov 8, 2026, 07:21 PM