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 boshi-xixixi/TraeSkill --skill az-cost-optimizegit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/az-cost-optimize)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/az-cost-optimize"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/az-cost-optimize.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.02963 |
| Opus 5 | $0.00018 | $0.01482 |
| Sonnet 5 | $0.00007 | $0.00593 |
| Haiku 4.5 | $0.00004 | $0.00296 |
Grade A, and why
az-cost-optimize 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- az-cost-optimize — 98% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Cost Optimize
This workflow analyzes Infrastructure-as-Code (IaC) files and Azure resources to generate cost optimization recommendations. It creates individual GitHub issues for each optimization opportunity plus one EPIC issue to coordinate implementation, enabling efficient tracking and execution of cost savings initiatives.
Prerequisites
- Azure MCP server configured and authenticated
- GitHub MCP server configured and authenticated
- Target GitHub repository identified
- Azure resources deployed (IaC files optional but helpful)
- Prefer Azure MCP tools (
azmcp-*) over direct Azure CLI when available
Workflow Steps
Step 1: Get Azure Best Practices
Action: Retrieve cost optimization best practices before analysis Tools: Azure MCP best practices tool Process:
- Load Best Practices:
- Execute
azmcp-bestpractices-getto get some of the latest Azure optimization guidelines. This may not cover all scenarios but provides a foundation. - Use these practices to inform subsequent analysis and recommendations as much as possible
- Reference best practices in optimization recommendations, either from the MCP tool output or general Azure documentation
- Execute
Step 2: Discover Azure Infrastructure
Action: Dynamically discover and analyze Azure resources and configurations Tools: Azure MCP tools + Azure CLI fallback + Local file system access Process:
- Resource Discovery:
- Execute
azmcp-subscription-listto find available subscriptions - Execute
azmcp-group-list --subscription <subscription-id>to find resource groups - Get a list of all resources in the relevant group(s):
- Use
az resource list --subscription <id> --resource-group <name>
- Use
- For each resource type, use MCP tools first if possible, then CLI fallback:
azmcp-cosmos-account-list --subscription <id>- Cosmos DB accountsazmcp-storage-account-list --subscription <id>- Storage accountsazmcp-monitor-workspace-list --subscription <id>- Log Analytics workspacesazmcp-keyvault-key-list- Key Vaultsaz webapp list- Web Apps (fallback - no MCP tool available)az appservice plan list- App Service Plans (fallback)az functionapp list- Function Apps (fallback)az sql server list- SQL Servers (fallback)az redis list- Redis Cache (fallback)- ... and so on for other resource types
- Execute
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.
- 8d ago First seen · 306 lines · 37 tokens per session scan A d27f8311b57d
az-cost-optimize is a skill published in the GitHub repository boshi-xixixi/TraeSkill (261 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 2,963 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-30.
Other skills, from other repositories
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
testing
A guide for writing tests that check observable behaviour rather than the code's internal structure. Tests are repeatable checks that confirm software still gives the expected result after changes.