Files
The-transit-Project/.github/agents/azure-deploy/prepare/references/subagent-pricing.md
T
Sven laptop 635a130f0b
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s
──────
### Summary of Changes
  1. Documentation Consolidation:
      • Relocated the docs/ folder and all repository .md files (README.md, DEPLOYMENT.md, DOCKER_README.md,
      DOMAINS_README.md, GETTING_STARTED.md, CI_CD_PORTAINER_GUIDE.md, ADMIN_DEPLOYMENT_SUMMARY.md,
      SECURITY_PRIVATE_FILES.md, handoff.md, azure-project-plan.md, plus service-specific READMEs) into .
      • Updated document links in README.md.
  2. AI Agent Project Map:
      • Created PROJECT_MAP.md in the project root containing complete architecture diagrams, service specs, ports, DB
      schemas, environment variables, and developer workflows.
      • Added PROJECT_MAP.md to .gitignore.
  3. Monitoring UI & Infrastructure Integration:
      • Added monitoring_ui service to docker-compose.yml (port 5175).
      • Configured Gitea workflow docker-build.yml for monitoring_ui builds.
      • Added CORS middleware headers in index.js.
      • Added nginx.conf copy step in Dockerfile.

  ──────
  ### Recommended Commit Message

    docs: consolidate project documentation into monitoring_ui and add agent project map

    - Move all markdown documentation files and docs/ folder into monitoring_ui/docs/
    - Update documentation hub index (monitoring_ui/docs/README.md) with relative paths
    - Generate comprehensive AI agent reference map (PROJECT_MAP.md) in repository root
    - Add PROJECT_MAP.md and monitoring_ui build output/env overrides to .gitignore
    - Integrate monitoring_ui service into docker-compose.yml and Gitea CI workflow
    - Configure CORS handling in employee_api for monitoring dashboard access
    ──────
  ### Alternative Short Commit Message

    refactor(docs): move docs to monitoring_ui and create AI agent PROJECT_MAP.md
2026-09-20 23:33:55 +02:00

3.0 KiB
Raw Blame History

Important: This skill provides guidance and recommended instructions to assist the AI system. Outputs are not guaranteed to be complete, correct, secure, or applicable to every scenario. Results should be reviewed and validated by a human before being applied. The AI model may choose not to follow all instructions exactly, and additional verification may be required.

Subagent Template — Cost Estimation (Step 6)

Estimate monthly costs for planned Azure services using Azure Retail Prices API.

References to Read Internally

Read BOTH before making any pricing calls:

Input (provided by caller)

Field Required
services[] with service type and selected SKU per service YES
region — deployment region YES
Budget tier (free / balanced / performance) YES

Output

Return JSON (≤500 tokens):

{
  "costEstimate": {
    "monthlyTotal": 42.50,
    "currency": "USD",
    "breakdown": [
      { "service": "App Service", "sku": "B1", "monthlyUsd": 13.14, "formula": "retailPrice × 730" },
      { "service": "PostgreSQL Flexible Server", "sku": "Standard_B1ms", "monthlyUsd": 24.82, "formula": "compute + storage" }
    ],
    "freeGrants": [
      { "service": "Container Apps", "grant": "180K vCPU-sec + 360K GiB-sec", "monthlySavings": 0 }
    ],
    "assumptions": [],
    "disclaimer": "Estimate based on Azure Retail Prices API. Verify at azure.com/pricing."
  }
}

Rules

  • ⛔ Do NOT invoke any other agents or hand off — no external agent calls of any kind. You are a pricing subagent only. Use direct HTTP to https://prices.azure.com/api/retail/prices for price queries (MCP pricing was already attempted inline by the caller).
  • ⛔ No $0 shortcut — compute always has cost (App Service B1 / SWA Standard / Functions Flex Consumption floor). Price every compute app via live API; note free grants (Cosmos free-tier account, Container Apps/Functions grants) but still price paid meters. Do NOT return $0 for a compute app.
  • ⛔ armSkuName is case-sensitive — use B1 not b1
  • ⛔ For services with empty armSkuName (Container Apps, Functions Flex Consumption, ACR, Storage, Cosmos): use filter/meterName matching — a sku filter returns []
  • ⛔ Monthly multiplier = each meter's unitOfMeasure (1 Hour→×730, 1/Day→×30 [ACR/registry, SQL DTU], 1 GB/Month→×GB, 1 Second→usage) — NEVER blanket ×730; applying ×730 to a 1/Day meter overstates ~24×
  • ⛔ Use direct HTTP to https://prices.azure.com/api/retail/prices for all price lookups. Do NOT use mcp_azure_mcp_pricing — it was already tried inline and failed.
  • ⛔ Never hardcode dollar amounts — always query live prices
  • ⛔ If pricing API returns 400: verify --sku included in the query

Token Budget

≤500 tokens for cost estimate report.