Back to skills
SKILL.md
1518 Cost Estimateinstructions C34071bf
ASecurityStandards for Azure cost estimate documentation with architecture and business context
- 9 stars
- 0 votes
- 0 copies
- 0 views
- Added October 11, 2026
Works with
Security analysis
100/100npx -y skills add tools-only/X-Skills --skill 1518-cost-estimateinstructions_c34071bf --agent claude-codeAre you the author of 1518 Cost Estimateinstructions C34071bf?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tools-only-1518-cost-estimateinstructions-c34071bf)---
description: "Standards for Azure cost estimate documentation with architecture and business context"
applyTo: "**/03-des-cost-estimate.md, **/07-ab-cost-estimate.md, **/docs/*-cost-estimate.md"
---
# Azure Cost Estimate Documentation Standards
## Document Purpose
Cost estimates provide:
- Financial clarity for budget approvals
- Architecture context linking cost to design decisions
- Optimization guidance for reducing costs
- Fast decisions via "what changes cost" tables
## General Requirements
- Keep markdown lines <= 120 characters.
- Use ATX headings (`##`, `###`) for sections.
- Use emoji callouts consistently (see "Visual Standards").
- Prefer tables for compare-and-decide content.
- If the workload is small, keep the same sections but shorten them.
## Canonical Templates (Golden Source)
The canonical cost-estimate structure is defined in these templates:
- `.github/skills/azure-artifacts/templates/03-des-cost-estimate.template.md` (design estimate)
- `.github/skills/azure-artifacts/templates/07-ab-cost-estimate.template.md` (as-built estimate)
Agents MUST start from the appropriate template and fill it in.
Do not re-embed long templates in agent bodies.
### Core Heading Contract (Stable)
Both templates MUST contain these exact H2 headings (`##`) in this order:
1. `## ๐ฐ Cost At-a-Glance`
2. `## โ
Decision Summary`
3. `## ๐ Requirements โ Cost Mapping`
4. `## ๐ Top 5 Cost Drivers`
5. `## Architecture Overview`
6. `## ๐งพ What We Are Not Paying For (Yet)`
7. `## โ ๏ธ Cost Risk Indicators`
8. `## ๐ฏ Quick Decision Matrix`
9. `## ๐ฐ Savings Opportunities`
10. `## Detailed Cost Breakdown`
Notes:
- Emoji + spacing must match exactly.
- Use the unicode arrow `โ` (not `->`) in the Requirements heading.
- Additional H2 headings are allowed, but discouraged (prefer H3s).
## Required Header
```markdown
# Azure Cost Estimate: {Project Name}
**Generated**: {YYYY-MM-DD}
**Region**: {primary-region}
**Environment**: {Production|Staging|Development}
**MCP Tools Used**: {azure_price_search, azure_cost_estimate, azure_bulk_estimate, azure_region_recommend, azure_sku_discovery}
**Architecture Reference**: {relative link to assessment doc, if available}
```
## ๐ฐ Cost At-a-Glance (Required)
Include immediately after the header:
````markdown
## ๐ฐ Cost At-a-Glance
> **Monthly Total: ~$X,XXX** | Annual: ~$XX,XXX
>
> ```
> Budget: $X/month (soft|hard) | Utilization: NN% ($X of $X)
> ```
>
> | Status | Indicator |
> | ----------------- | ---------------------------- |
> | Cost Trend | โก๏ธ Stable |
> | Savings Available | ๐ฐ $X/year with reservations |
> | Compliance | โ
{e.g., PCI-DSS aligned} |
````
If no budget is provided, use:
- `Budget: No fixed budget (explain in one sentence)`
## โ
Decision Summary (Required)
Immediately after "Cost At-a-Glance", include a 2-3 bullet decision summary:
- What's approved now
- What's deferred (intentionally not paying for yet)
- What requirement change would trigger a redesign
Also include a confidence line:
```markdown
**Confidence**: High|Medium|Low | **Expected Variance**: ยฑX% (1 sentence why)
```
## Visual Standards
### Status Indicators
| Status | Indicator | Usage |
| -------------- | --------- | ------------------------------------- |
| Under budget | โ
| < 80% utilized |
| Near budget | โ ๏ธ | 80-100% utilized |
| Over budget | โ | > 100% utilized |
| Recommendation | ๐ก | Optimization suggestions |
| Savings | ๐ฐ | Money saved |
| High risk | ๐ด | Potential to materially increase cost |
| Medium risk | ๐ก | Could increase cost under growth |
| Low risk | ๐ข | Predictable |
### Category Icons
| Category | Emoji |
| ------------------- | ----- |
| Compute | ๐ป |
| Data Services | ๐พ |
| Networking | ๐ |
| Messaging | ๐จ |
| Security/Management | ๐ |
### Trend Indicators
- โก๏ธ Stable
- ๐ Increasing
- ๐ Decreasing
- โ ๏ธ Volatile/unknown
## Required Sections (Recommended Order)
### 1. โ
Decision Summary
```markdown
## โ
Decision Summary
- โ
Approved: {what is in-scope and funded}
- โณ Deferred: {what is explicitly not included yet}
- ๐ Redesign Trigger: {what requirement change forces SKU/region redesign}
**Confidence**: High|Medium|Low | **Expected Variance**: ยฑX% (1 sentence why)
```
### 2. ๐ Requirements โ Cost Mapping
Map business requirements and NFRs to concrete SKU decisions.
```markdown
## ๐ Requirements โ Cost Mapping
| Requirement | Architecture Decision | Cost Impact | Mandatory |
| ----------- | --------------------- | ------------ | --------- |
| SLA 99.9% | Use {service/SKU} | +$X/month ๐ | Yes |
| RTO/RPO | {backup/DR choice} | +$X/month | No |
| Compliance | {WAF/PE/CMK choice} | +$X/month ๐ | Yes |
```
### 3. ๐ Top 5 Cost Drivers
```markdown
## ๐ Top 5 Cost Drivers
| Rank | Resource | Monthly Cost | % of Total | Trend |
| ---- | -------- | ------------ | ---------- | ----- |
| 1๏ธโฃ | ... | $... | ... | โก๏ธ |
> ๐ก **Quick Win**: One low-effort action that saves meaningful cost
```
### 4. Summary
```markdown
## Summary
| Metric | Value |
| ------------------- | ----------------- |
| ๐ต Monthly Estimate | $X - $Y |
| ๐
Annual Estimate | $X - $Y |
| ๐ Primary Region | swedencentral |
| ๐ณ Pricing Type | List Price (PAYG) |
| โญ WAF Score | X.X/10 (or TBD) |
| ๐ฏ Target Users | N concurrent |
```
Add a short "Business Context" narrative (2-5 lines) linking spend to outcomes.
### 5. Architecture Overview
Include both subsections:
1. Cost distribution (table + optional generated image)
2. Key design decisions affecting cost
Cost distribution is required for all workloads. Preferred format is a markdown table.
Optional: include a generated chart image (PNG/SVG) when available.
```markdown
## Architecture Overview
### Cost Distribution
| Category | Monthly Cost (USD) | Share |
| ---------------- | -----------------: | ----: |
| ๐ป Compute | 535 | 39% |
| ๐พ Data Services | 466 | 34% |
| ๐ Networking | 376 | 27% |

```
### Key Design Decisions Affecting Cost
| Decision | Cost Impact | Business Rationale | Status |
| -------- | -------------- | ------------------ | -------- |
| ... | +$.../month ๐ | ... | Required |
````text
### 6. ๐งพ What We Are Not Paying For (Yet)
Make trade-offs explicit so stakeholders see conscious deferrals.
```markdown
## ๐งพ What We Are Not Paying For (Yet)
> Examples: multi-region active-active, private endpoints for all services, premium HA cache, DDoS Standard
```
### 7. โ ๏ธ Cost Risk Indicators
```markdown
## โ ๏ธ Cost Risk Indicators
| Resource | Risk Level | Issue | Mitigation |
| -------- | ---------- | ----- | ---------- |
| ... | ๐ด High | ... | ... |
> **โ ๏ธ Watch Item**: One sentence on the biggest budget uncertainty
````
### 8. ๐ฏ Quick Decision Matrix
```markdown
## ๐ฏ Quick Decision Matrix
_"If you need X, expect to pay Y more"_
| Requirement | Additional Cost | SKU Change | Notes |
| ----------- | --------------- | ---------- | ----- |
| ... | +$.../month | ... | ... |
```
### 9. ๐งฉ Change Control (Top 3 Change Requests)
Standardize the 3 most likely changes and their delta.
```markdown
## ๐งฉ Change Control
| Change Request | Delta | Notes |
| ------------------- | --------- | -------------------- |
| Add multi-region DR | +$X/month | From decision matrix |
| Add WAF | +$X/month | From decision matrix |
| Upgrade DB tier | +$X/month | From decision matrix |
```
### 10. ๐ฐ Savings Opportunities
Always include a savings section.
If already optimized, say so and list what is already applied.
```markdown
## ๐ฐ Savings Opportunities
> ### Total Potential Savings: $X/year
>
> | Commitment | Monthly Savings | Annual Savings |
> | ---------- | --------------- | -------------- |
> | 1-Year ... | $... | $... |
### Additional Optimization Strategies
| Strategy | Potential Savings | Effort | Notes |
| -------- | ----------------- | ------ | ----- |
| ... | ... | ๐ข Low | ... |
```
### 11. Detailed Cost Breakdown
Break down by category, include subtotals.
```markdown
## Detailed Cost Breakdown
### ๐ป Compute Services
| Resource | SKU | Qty | $/Hour | $/Month | Notes |
| -------- | --- | --- | ------ | ------- | ----- |
**๐ป Compute Subtotal**: ~$X/month
```
### 12. ๐ Monthly Cost Summary
Include:
- A category summary table
- An ASCII bar distribution (simple, readable)
### 13. ๐งฎ Base Run Cost vs Growth-Variable Cost
Make variance drivers explicit.
```markdown
## ๐งฎ Base Run Cost vs Growth-Variable Cost
| Cost Type | Drivers | Examples | How It Scales |
| --------------- | ----------- | -------------------------- | ----------------------------- |
| Base run | fixed SKUs | App Service plan, SQL tier | step-changes (SKU upgrades) |
| Growth-variable | usage-based | egress, logs, queries | linear/near-linear with usage |
```
### 14. ๐ Regional Comparison
Include the primary region and at least one alternative.
Add one sentence explaining why the primary was chosen.
### 15. ๐ง Environment Strategy (FinOps)
Explicitly state prod vs non-prod sizing rules and whether non-prod auto-shutdown is used.
```markdown
## ๐ง Environment Strategy (FinOps)
- Production: {HA/zone strategy, baseline capacity}
- Non-prod: {smaller SKUs, single instance, auto-shutdown schedule}
```
### 16. ๐ Environment Cost Comparison
If there are multiple environments (prod/staging/dev), include the table.
If single environment, include a short table and state "single environment".
### 17. ๐ก๏ธ Cost Guardrails
Tie the estimate to operational enforcement.
```markdown
## ๐ก๏ธ Cost Guardrails
| Guardrail | Threshold | Action |
| -------------- | ----------- | ------------------------ |
| Budget alert | 80% / 100% | Notify / block approvals |
| DB utilization | >80% | Review tier/queries |
| Log ingestion | >X GB/day | Tune sampling/retention |
| Egress | >X GB/month | Investigate CDN/traffic |
```
### 18. ๐ Testable Assumptions
List 3-5 assumptions most likely to change spend, and how to measure them.
```markdown
## ๐ Testable Assumptions
| Assumption | Why It Matters | How to Measure | Threshold / Trigger |
| ------------------ | -------------------------- | ------------------------- | ------------------- |
| Egress < 100 GB/mo | keeps networking costs low | Azure Cost Mgmt + metrics | >100 GB/mo |
| Logs < 5 GB/mo | avoids ingestion costs | Log Analytics usage | >5 GB/mo |
```
### 19. ๐ Pricing Data Accuracy
Required bullets:
- Usage basis (e.g., 730 hours/month)
- Pricing type (PAYG list price unless otherwise stated)
- Data/egress assumptions
- Prices queried date
### 19. ๐ Pricing Data Accuracy
```markdown
## ๐ Pricing Data Accuracy
> **๐ Data Source**: Prices retrieved from Azure Retail Prices API via Azure Pricing MCP
>
> โ
**Included**: Retail list prices (PAYG)
>
> โ **Not Included**: EA discounts, CSP pricing, negotiated rates, Azure Hybrid Benefit
>
> ๐ก For official quotes, validate with Azure Pricing Calculator
```
### 20. ๐ References
Always include links to:
- Azure Pricing Calculator
- Azure Retail Prices API
- Any assessment/plan/docs used
## Pricing Sources (Priority Order)
1. Azure Pricing MCP (`azure_price_search`, `azure_cost_estimate`, `azure_bulk_estimate`)
2. Azure Pricing Calculator (manual validation)
3. Azure Retail Prices API (programmatic)
## Patterns to Avoid
| Anti-Pattern | Solution |
| ---------------------- | -------------------------------------------------- |
| Missing cost drivers | Include top 5 drivers table |
| Missing assumptions | Document usage and pricing basis |
| No "what changes cost" | Include the decision matrix |
| No risk callouts | Include cost risk indicators + a watch item |
| No savings section | Always include savings and what is already applied |
| Stale prices | Note query date; re-validate periodically |
| Missing change control | Include top 3 likely change requests + delta |
| Hidden trade-offs | Add "What we are not paying for (yet)" |
| Unclear variance | Add confidence, variance, base vs variable split |
Attribution
Comments
Loading commentsโฆ