oma-orchestrator
Fail
Audited by Gen Agent Trust Hub on May 16, 2026
Risk Level: HIGHCOMMAND_EXECUTIONPROMPT_INJECTIONEXTERNAL_DOWNLOADS
Full Analysis
- [COMMAND_EXECUTION]: The orchestrator's configuration in
config/cli-config.yamlexplicitly enables unsafe execution modes for various AI CLI tools. It uses flags such as--dangerously-skip-permissionsfor Claude Code and--yoloor--full-autofor Gemini, Qwen, Codex, and Cursor. This bypasses the security models of these platforms, allowing autonomous agents to execute shell commands and modify the filesystem without human-in-the-loop verification. - [PROMPT_INJECTION]: The skill is highly susceptible to indirect prompt injection. It ingests data from untrusted sub-agent outputs (
result-{agent-id}-{sessionId}.md) and progress files, which are then interpolated into subsequent prompts viaresources/subagent-prompt-template.mdwithout sanitization. - Ingestion points: Result and progress files stored in the
.serena/memoriespath. - Boundary markers: The system relies on standard markdown headers but lacks instructions for the orchestrator to disregard potentially malicious commands embedded in agent results.
- Capability inventory: The skill has the ability to spawn arbitrary processes and write to the local filesystem across the entire codebase.
- Sanitization: No input validation or escaping is applied to the task descriptions or sub-agent results before they are used to build new task boards or prompts.
- [COMMAND_EXECUTION]: The provided scripts (
scripts/spawn-agent.sh,scripts/parallel-run.sh,scripts/verify.sh) useexecto pass all arguments directly to theomaCLI tool. This pattern can lead to command injection if agent IDs or session IDs are manipulated to include shell metacharacters.
Recommendations
- AI detected serious security threats
Audit Metadata