The Agent Skills Directory

DATA_EXFILTRATION (HIGH): The docker_compose_template.txt file configures a volume mount from $HOME/.azure on the host to /root/.azure inside the container. This exposes the user's host-level Azure CLI credentials, tokens, and configuration profiles to any code running within the container, creating a high risk of credential theft if the containerized environment is compromised.
REMOTE_CODE_EXECUTION (HIGH): The dockerfile_template.txt file uses a piped shell pattern to install the Azure CLI: curl -sL https://aka.ms/InstallAzureCLIDeb | bash. Although aka.ms is a Microsoft-owned domain, this pattern is inherently insecure as it executes remote code directly without integrity verification. Per the analysis rules, while the trusted source status of Microsoft downgrades the download itself to LOW, the behavior of piped execution remains a HIGH risk finding.
COMMAND_EXECUTION (MEDIUM): The tiltfile_template.txt uses Tilt's run() and local_resource() functions to execute shell commands on the host or inside containers based on file triggers. This includes complex command chains like poetry export ... && pip install ... which are dynamically constructed and executed.
DYNAMIC_EXECUTION (MEDIUM): The init_azurite_template.sh script executes an embedded Python script via a shell heredoc. While this is used for initialization, it represents a pattern of executing unvalidated script content at runtime within the container.
CREDENTIALS_UNSAFE (LOW): The init_azurite_template.sh and local_settings_template.txt files contain or reference a hardcoded default Azurite account key (Eby8vdM02xNO...). While this is the standard publicly known key for the Azurite emulator, its presence in templates can lead to accidental use in non-development environments if not carefully managed.

generate-azure-functions