orca-graph
Pass
Audited by Gen Agent Trust Hub on Sep 20, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONPERSISTENCEDYNAMIC_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill relies on external 'PLAN.md' files which contain instructions and executable commands that are parsed and run by the agent.
- Ingestion points: The
PLAN.mdfile serves as the primary input for thebuild,run, andnextoperations, where it is parsed for task metadata and logic. - Boundary markers: None. The skill extracts commands based on standard Markdown bold patterns (e.g.,
**Verify:**,**QC:**) without explicit delimiters to separate untrusted content from the execution engine. - Capability inventory: The skill executes arbitrary shell commands via the
orca-graph.pyscript, manages a background daemon process, performs file system operations (writes toevents.jsonland project graphs), and executes Git commands (git checkout). - Sanitization: There is no explicit sanitization or validation of the command strings extracted from the plan file before they are passed to the shell.
- [COMMAND_EXECUTION]: The skill provides a mechanism to execute arbitrary shell commands provided as arguments to the
runcommand or defined within thePLAN.mdfile under**Verify:**and**QC:**headers. This is a core feature of the orchestrator but represents a direct command execution sink. - [PERSISTENCE]: The
watchandruncommands implement a persistence mechanism by spawning a background daemon process. This daemon tracks project states across the machine and maintains a global registry file at~/.orca-graph/registry.jsonto coordinate task execution across different sessions. - [DYNAMIC_EXECUTION]: The skill dynamically generates and executes shell commands at runtime based on the task graph's state. This includes the automated execution of verification scripts and the optional
**QC:**(Quality Control) review commands that run after a task is completed.
Audit Metadata