jira-todo
Pass
Audited by Gen Agent Trust Hub on Sep 17, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTION
Full Analysis
- [COMMAND_EXECUTION]: The skill uses the
Bashtool to executejiraandgitcommands (e.g.,jira me,jira issue list,git branch). It also reads the local Jira configuration file located at~/.config/.jira/.config.ymlto extract project settings, which is standard for the tool's primary purpose.\n- [INDIRECT_PROMPT_INJECTION]: The skill processes external data from Jira ticket summaries, descriptions, and comments, which constitutes a potential attack surface.\n - Ingestion points: External data is ingested through the standard output of
jira issue listcommands in Phase 3.\n - Boundary markers: No explicit boundary markers or instructions to ignore embedded commands are present in the processing logic.\n
- Capability inventory: The skill has access to
Bash,Read,Task, andTodoWritetools, enabling file system interaction and command execution.\n - Sanitization: The skill does not explicitly sanitize or escape ticket content before including it in the generated report, which could allow malicious content in a Jira ticket to influence the agent's behavior at runtime.\n- [DYNAMIC_EXECUTION]: The evaluation scenarios in
evals/evals.jsoninvolve instructions for the agent to create executable mock scripts and modify the systemPATHto simulate the environment during testing.
Audit Metadata