azure-app-onboard-prereq
Pass
Audited by Gen Agent Trust Hub on Aug 19, 2026
Risk Level: SAFEPROMPT_INJECTIONCOMMAND_EXECUTION
Full Analysis
- Indirect Prompt Injection Surface: The skill evaluates user-provided repository files, including project manifests and source code, to assess Azure deployment readiness. This ingestion of untrusted data represents a surface for indirect prompt injection where malicious content in a repository could attempt to influence the agent's behavior.
- Ingestion points: The skill reads repository manifests (e.g., package.json, requirements.txt) and up to 20 source files per component to detect tech stacks and build health.
- Boundary markers: The instructions do not specify explicit delimiters or markers to isolate ingested repository data from the agent's internal system prompts.
- Capability inventory: The agent has access to tools for file creation and modification within the session directory, terminal access for Azure CLI and Git, and the ability to execute package manager commands (e.g., npm install) if explicitly approved by the user.
- Sanitization: The skill focuses on static analysis patterns and imposes strict human-in-the-loop gates for all command execution and remediation steps, which serves to mitigate the risk of autonomous malicious actions.
- Command Execution Patterns: The skill utilizes terminal commands such as
az account showandgit rev-parse HEADto gather environment and repository state information. - What it does: These commands are used to validate the Azure subscription context and track repository versions to prevent the use of stale analysis.
- Context: These operations are restricted to information gathering necessary for the skill's primary function and are standard for development and deployment utilities.
- File System Access: The skill manages session state by writing artifacts (context.json, prereq-output.json) to the
.copilot-azure/directory. - What it does: It creates and modifies files to maintain analysis results and session history across different phases of the onboarding process.
- Context: File operations are scoped to a specific, session-related directory and are used for metadata and report persistence rather than system-wide changes.
Audit Metadata