denji
Warn
Audited by Gen Agent Trust Hub on Oct 8, 2026
Risk Level: MEDIUMCOMMAND_EXECUTIONDYNAMIC_EXECUTIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The Denji CLI tool documentation describes a
hooksfeature within thedenji.jsonconfiguration file. This allows for the execution of arbitrary shell commands during lifecycle events such aspostAddandpostRemove. While primarily intended for automation (e.g., running formatters), it provides a mechanism for command execution defined in a project-local file.\n - Evidence: Found in
SKILL.mdandreferences/configuration.md. The documentation explicitly lists examples such asnpx biome check --writeandnpx prettier --writeas hook commands.\n- [DYNAMIC_EXECUTION]: The skill enables the dynamic execution of shell scripts or commands defined in thedenji.jsonconfiguration file at runtime whenever the CLI performs specified actions.\n - Evidence: The
hooksproperty in thedenji.jsonschema is detailed inreferences/configuration.mdas an array of commands executed by the CLI.\n- [INDIRECT_PROMPT_INJECTION]: Thedenji importcommand allows the ingestion of icon data from external JSON or text files, creating a vulnerability surface where maliciously crafted data files could attempt to influence the agent's behavior if processed unsafely.\n - Ingestion points:
denji importreads manifest data from files or stdin as described inSKILL.md.\n - Boundary markers: The documentation does not specify the use of delimiters or warnings to isolate imported data from the agent's instructions.\n
- Capability inventory: The skill has the capability to execute shell commands via its
hookssystem and modify project files.\n - Sanitization: No explicit sanitization or validation logic for the content of imported files is documented.
Audit Metadata