Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add alexpizarro/azure-lean-stack-skills --skill configuring-azure-oidc-for-github-actionsgit clone --depth 1 https://github.com/alexpizarro/azure-lean-stack-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/alexpizarro/azure-lean-stack-skills/configuring-azure-oidc-for-github-actions)<a href="https://agentmods.dev/skills/alexpizarro/azure-lean-stack-skills/configuring-azure-oidc-for-github-actions"><img src="https://agentmods.dev/badge/skills/alexpizarro/azure-lean-stack-skills/configuring-azure-oidc-for-github-actions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alexpizarro/azure-lean-stack-skills/configuring-azure-oidc-for-github-actions"><img src="https://agentmods.dev/badge/skills/alexpizarro/azure-lean-stack-skills/configuring-azure-oidc-for-github-actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.01336 |
| Opus 5 | $0.00039 | $0.00668 |
| Sonnet 5 | $0.00016 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
configuring-azure-oidc-for-github-actions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring Azure OIDC for GitHub Actions
Sets up secret-less Azure authentication for GitHub Actions. After running these scripts, deploys work via git push with no client secrets to rotate.
Why OIDC
- No client secrets stored in GitHub or in code
- Branch-scoped: the
testSP can't deploy toproductionand vice versa - Federated credential subject is bound to
refs/heads/{branch}exactly — drift causesAADSTS70021
Workflow checklist
Copy this checklist into your response and check items off as you complete them:
OIDC + GitHub Actions setup:
- [ ] Step 1: Verify az login + gh auth login (and AZURE_CONFIG_DIR if shared machine)
- [ ] Step 2: Confirm GitHub repo exists, branches (test, production) created
- [ ] Step 3: Run scripts/create-sp-with-oidc.sh → creates test + prod SPs + federated creds
- [ ] Step 4: Run scripts/generate-sql-password.sh → SQL admin passwords
- [ ] Step 5: Run scripts/add-github-secrets.sh → 6 secrets set
- [ ] Step 6: For each additional environment branch (acme-demo, customer-uat, etc.), re-run with that branch name
- [ ] Step 7: First push to test → verify the workflow authenticates (no AADSTS70021)
Setup sequence
Run these scripts in order. Each is idempotent (safe to re-run).
# Prerequisites: az login and gh auth login already done.
# Use AZURE_CONFIG_DIR if this project shares a machine with others.
export ORG="acme" # short org prefix
export PROJECT="taskapp" # short project name
export GITHUB_ORG="myorg"
export REPO="taskapp"
# 1. Create both service principals + federated credentials
bash scripts/create-sp-with-oidc.sh
# 2. Generate SQL admin passwords (test + prod)
bash scripts/generate-sql-password.sh
# 3. Set the 6 GitHub secrets
bash scripts/add-github-secrets.sh
Each script prints what it will do, what already exists, and what was created.
The 6 GitHub secrets
| Secret | Scope | Source |
|---|---|---|
AZURE_TENANT_ID |
Both envs | az account show --query tenantId |
AZURE_SUBSCRIPTION_ID |
Both envs | az account show --query id |
AZURE_CLIENT_ID_TEST |
Test SP appId | create-sp-with-oidc.sh output |
AZURE_CLIENT_ID_PROD |
Prod SP appId | create-sp-with-oidc.sh output |
SQL_ADMIN_PASSWORD_TEST |
Test SQL admin | generate-sql-password.sh output |
SQL_ADMIN_PASSWORD_PROD |
Prod SQL admin | generate-sql-password.sh output |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 125 lines · 78 tokens per session scan A b8e83835f8ee
configuring-azure-oidc-for-github-actions is a skill published in the GitHub repository alexpizarro/azure-lean-stack-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,336 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
azure-kubernetes-app-deploy
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster…
bitbucket
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines.
jenkins
Jenkins CI/CD integration for investigating builds, deployments, pipeline stages, and test results during RCA.
azure-validate
WORKFLOW SKILL — Pre-deployment validation for Azure: config, infrastructure (Bicep/Terraform), permissions, prerequisites. WHEN: 'validate my app', 'check deployment readiness', 'run preflight checks', 'validate azure.yaml', 'validate Bicep', 'test before deploying', 'validate Azure Functions'. DO NOT USE FOR…
azure-expert
Expert-level Microsoft Azure cloud platform, services, and architecture. Use when the user mentions cloud, Microsoft platforms, Azure Functions, or Cosmos DB.