kienbui1995/magic-powers/ado-pipeline-security
Claude Code and agent skill by kienbui1995/magic-powers
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when hardening Azure Pipelines security — YAML pipeline permissions, fork build security, resource authorization, secret scanning, protected resources, and preventing pipeline-based attacks.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-pipeline-securitySKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-pipeline-security.
ADO Pipeline Security
When to Use
- Reviewing pipeline security before production use
- Hardening pipelines against secret exfiltration
- Configuring fork PR build security for open source repos
- Auditing which pipelines can access service connections
- Implementing least-privilege pipeline permissions
- Responding to a pipeline security incident or audit finding
Core Jobs
1. Secret Management in Pipelines
Secret hygiene rules:
- Secrets from Key Vault-linked variable groups are auto-masked in logs
- Never pass secrets as command-line arguments (visible in
ps auxon agent) - Use environment variables to inject secrets into processes
- Enable "Audit" on secret variable groups to track access in the audit log
- Mark variables as secret in the pipeline UI — they cannot be printed even accidentally
2. Fork Build Security
Fork PR security settings (Project Settings → Pipelines → Settings):
- "Comment required before running pipeline for outside contributors" — manual maintainer review before fork PR pipeline runs; prevents malicious pipelines from auto-executing
- Limit secrets to forks — forks cannot access service connections or variable group secrets (enforced by default, do not disable)
- "No access" for fork contributions to sensitive variable groups — verify in Library → variable group → Pipeline permissions
3. Resource Authorization (Least-Privilege Service Connections)
Restrict service connection access (Azure DevOps UI):
Service connection best practices:
- Use service principal with minimum required RBAC role (e.g.
Contributoron one resource group, not subscription) - Rotate service principal credentials on a schedule (or use federated credentials — no secret to rotate)
- Never use personal account credentials in service connections (leaves when employee departs)
- Production service connections: authorize only 1-2 specific release pipelines, never "all pipelines"
4. YAML Pipeline Isolation
5. Pipeline YAML Security Review
6. Audit & Compliance Checks
Key Concepts
- Secret masking — Azure DevOps automatically replaces secret variable values with
***in pipeline logs; only works if variable is marked secret - Fork security — contributors on forked repos can modify pipeline YAML; the fork pipeline runs with access to the fork's YAML, treat as untrusted code
- Resource authorization — a pipeline must be explicitly authorized to use service connections, agent pools, variable groups, and environments; first use triggers authorization prompt
- Container jobs — run pipeline job inside a Docker container for filesystem isolation from the host agent
- Protected resources — service connections, agent pools, variable groups, secure files, and environments with access controls configured
- Federated credentials — service principal authentication without a client secret; uses OIDC token from Azure DevOps (no credential to rotate or leak)
Checklist
- [ ] No secrets hardcoded in pipeline YAML variables (use Key Vault-linked variable groups)?
- [ ] Secrets passed as environment variables to processes (not command-line arguments)?
- [ ] Fork PR builds require maintainer comment approval before running?
- [ ] Production service connections restricted to specific named pipelines (not "all pipelines")?
- [ ] Pipeline YAML stored in repo and version-controlled (auditable history)?
- [ ]
checkout: nonein deploy jobs (source code not needed at deploy time)? - [ ] Service connections use service principal (not personal account or admin credentials)?
- [ ] No
curl | bashpatterns in pipeline scripts (supply chain risk)?
Key Outputs
- Pipeline security review report covering secrets, permissions, fork settings, and resource authorization
- Production service connections restricted to authorized pipelines only
- Fork PR security configured to require maintainer approval before pipeline execution
- Container jobs implemented for build isolation where agent trust is a concern
Output Format
- 🔴 Critical — secrets hardcoded in YAML or echoed to logs, production service connections accessible to all pipelines, fork PRs running without maintainer approval on public repos
- 🟡 Warning — service connections using personal account PATs instead of service principal, no periodic review of pipeline resource authorization,
curl | bashpatterns in scripts - 🟢 Suggestion — use container jobs for build isolation, implement federated credentials to eliminate secret rotation, audit pipeline permissions on a quarterly schedule
Anti-Patterns
echo $(SECRET_VARIABLE)in scripts — even with masking, some debug log modes can reveal values- "Allow all pipelines" on production service connections — any new pipeline immediately gets production access
- Classic build pipelines for new work — not version-controlled, not reviewable via PR, harder to audit
- Storing pipeline artifacts that include source code alongside build outputs (may contain sensitive config)
- Using the same service connection for dev and production (blast radius of leaked credential includes production)
Integration
ado-pipeline-design— security principles applied to the pipeline structure designed thereado-pipelines-ops— service connection setup with least-privilege RBAC rolesado-security-policies— branch policies and organization security settings that complement pipeline security
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ado-pipeline-security/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kienbui1995/magic-powers/ado-pipeline-security)