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 Ahtesham-Latif/Tie-Breaker-App --skill azure_deploymentgit clone --depth 1 https://github.com/Ahtesham-Latif/Tie-Breaker-AppWrote 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/ahtesham-latif/tie-breaker-app/azure_deployment)<a href="https://agentmods.dev/skills/ahtesham-latif/tie-breaker-app/azure_deployment"><img src="https://agentmods.dev/badge/skills/ahtesham-latif/tie-breaker-app/azure_deployment/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/ahtesham-latif/tie-breaker-app/azure_deployment"><img src="https://agentmods.dev/badge/skills/ahtesham-latif/tie-breaker-app/azure_deployment.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.00042 | $0.00775 |
| Opus 5 | $0.00021 | $0.00387 |
| Sonnet 5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
azure-nodejs-deployment-via-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 11d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure App Service Deployment (Node.js)
This skill outlines the flawless, best-practice path to deploy a Node.js application to Azure App Service (Linux) while securely connecting to an Azure AI Foundry agent via Managed Identity.
1. Cloud Infrastructure Setup
- App Service Plan: Always choose a dedicated tier (e.g., Basic B1) for production. Free (F1) tiers have strict 60-minute daily CPU quotas that will forcefully shut down the application (Resulting in a
403 Stoppederror).
2. Authentication & Managed Identity (Passwordless)
- Code: Use
DefaultAzureCredentialfrom@azure/identityin the Node.js backend. - Enable Identity: In the Azure App Service portal, go to Settings > Identity and enable System assigned.
- IAM Permissions: In the target Azure AI Project, go to Access control (IAM) and assign the Azure AI Developer role to the App Service's Managed Identity. (Note:
Cognitive Services OpenAI Useris not sufficient for Azure Foundry Orchestration Agents).
3. Environment Variables (The Frontend vs Backend Trap)
When deploying a full-stack app (React/Vite + Node.js) via GitHub Actions, environment variables must be split logically:
The Frontend (Vite)
- Variables prefixed with
VITE_(e.g., Supabase keys) are baked into the static HTML/JS at build time. - Where to set them: They MUST be stored in GitHub Secrets and explicitly mapped in your
.github/workflowsfile under theenv:block for thenpm run buildstep. - Danger: If they are only in Azure and not in GitHub Actions, Vite will build the frontend with empty variables.
The Backend (Node.js)
- The live
server.jsfile reads environment variables at runtime from the cloud container. - Where to set them: Configure variables (e.g., Azure AI endpoints, Backend Supabase keys) directly in the Azure Portal under Settings > Environment variables.
- Danger: The Azure App Service backend does NOT inherit your GitHub Actions secrets. You must set them in the Azure Portal manually.
- Crucial: Variables are loaded into memory exactly once when the Node.js process starts. If a variable is added or changed, you must explicitly click Restart on the App Service Overview page.
- To trust the Azure Load Balancer (required for
express-rate-limit), ensure the Express app hasapp.set('trust proxy', 1);.
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.
- 11d ago First seen · 41 lines · 42 tokens per session scan A 8404a2265f34
azure-nodejs-deployment-via-github-actions is a skill published in the GitHub repository Ahtesham-Latif/Tie-Breaker-App (1 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 775 once invoked, about $0.0002 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
use-vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI. Use when the user asks to deploy to Vercel from GitHub Actions, add Vercel preview deploys, post a Vercel preview URL on a PR, configure prebuilt Vercel deployments, set up alias domains for previews, create a GitHub…
infra-kit.workflow.audit
Review infrastructure-as-code, DevOps pipelines, and platform controls for security, reliability, compliance, and delivery hygiene using cloud well-architected baselines.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.