agentleFS
MicrosoftKnown publishermicrosoft/azure-skills/.github/plugins/azure-cost/skills/cost-estimation/SKILL.md

cost-estimation

Skill1.6k starsChanged 16 days agoMITView on GitHub

Forecast Azure spend and price planned resources or workloads. WHEN: \"forecast Azure spending\", \"project next month cost\", \"compare forecast to my planning target\", \"how much will Azure cost\", \"estimate VM cost\", \"compare storage tiers\", \"compare Azure regions\", \"retail price\", \"EA rate card\", \"negotiated pricesheet\". DO NOT USE FOR: configured budget health or alerts, bill analysis, cost spikes, rightsizing, or commitments.

6 other projects use a version of this, 1 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 3 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 21 mentionsNov 2026: 24 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/azure-skills repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about microsoft/azure-skills

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for forecasts, pricing, and planning targets.

    line 21
  2. Distinctive:

    Never transform MCP results in a shell or interpreter.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Azure Cost Estimation

Quick Reference

IntentWorkflowPrimary tools
Forecast existing spendCost forecastforecast_costs
Price planned resourcesPricing estimatePricing tools

When to Use This Skill

Use for forecasts, pricing, and planning targets.

MCP Tools

ToolUse
forecast_costsForecast a scope.
get_retail_pricesGet public prices.
start_pricesheet_download, get_pricesheet_statusGet Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) prices.

Fallback: API mappings.

Workflow

  1. Distinguish forecasts from hypothetical pricing.
  2. Confirm scope, assumptions, period, region, OS, and currency.
  3. Load the matching workflow and label every value type.
  4. Never transform MCP results in a shell or interpreter; request tool-side filtering or bounded follow-up queries.

Error Handling

ErrorAction
Ambiguous meterAsk for OS, term, tier, or usage.
Forecast unavailableExplain the history requirement.
Pricesheet pendingHonor the returned polling interval.
Multiple currenciesNever combine currencies.
Server errorRetry once; then report the trace ID.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.