azure-devops-cli

Pass

Audited by Gen Agent Trust Hub on Apr 14, 2026

Risk Level: SAFECOMMAND_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
  • [COMMAND_EXECUTION]: The skill provides numerous examples of az CLI commands for managing Azure DevOps projects, pipelines, repositories, and security configurations. These commands are consistent with the skill's intended purpose and follow documented CLI usage.\n- [EXTERNAL_DOWNLOADS]: The skill contains a reference to the official Microsoft Azure CLI installation script (https://aka.ms/InstallAzureCLIDeb). This is a trusted source and follows standard deployment procedures for the required tooling.\n- [CREDENTIALS_UNSAFE]: The skill adheres to safe credential management practices. It uses placeholders like YOUR_PAT_TOKEN and demonstrates how to use environment variables to supply sensitive credentials to automated scripts, avoiding hardcoded secrets.\n- [PROMPT_INJECTION]: The skill has an indirect prompt injection surface as it processes data from Azure DevOps environments (such as pull request descriptions or work item titles) which could contain untrusted input.\n
  • Ingestion points: az repos pr show, az boards work-item show, and az pipelines runs show.\n
  • Boundary markers: None explicitly used in the reference scripts.\n
  • Capability inventory: Shell command execution via the Azure CLI and curl, as well as local file writing capabilities.\n
  • Sanitization: Not explicitly documented in the provided reference scripts, as they rely on standard shell variable interpolation.\n- [DATA_EXFILTRATION]: Workflow examples include the use of curl to send notifications to external webhooks (e.g., Slack). This is a standard automation pattern for CI/CD alerting and is used here in a legitimate context.
Audit Metadata
Risk Level
SAFE
Analyzed
Apr 14, 2026, 07:30 AM
Security Audit — agent-trust-hub — azure-devops-cli