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.
git clone --depth 1 https://github.com/getnable/finopsmcpWrote 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/plugins/getnable/finopsmcp/nable)<a href="https://agentmods.dev/plugins/getnable/finopsmcp/nable"><img src="https://agentmods.dev/badge/plugins/getnable/finopsmcp/nable/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/plugins/getnable/finopsmcp/nable"><img src="https://agentmods.dev/badge/plugins/getnable/finopsmcp/nable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nable 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 17d 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.
What it actually says
{
"name": "nable",
"displayName": "nable, local-first FinOps",
"version": "0.10.0",
"description": "Prices what your coding agent is about to do before it runs: asks before costly launches and destroys, tracks AI spend, and answers cost questions across AWS, Azure, GCP, Kubernetes and AI providers. Local, read-only. The guard is on once the plugin is installed; nable guard off pauses it. Credentials stay on your machine.",
"author": {
"name": "Chandan Bukkapatnam",
"email": "[email protected]",
"url": "https://getnable.com"
},
"homepage": "https://getnable.com",
"repository": "https://github.com/getnable/finopsmcp",
"license": "Apache-2.0",
"keywords": [
"finops",
"aws",
"azure",
"gcp",
"cost",
"kubernetes",
"llm",
"mcp"
],
"mcpServers": {
"nable": {
"command": "uvx",
"args": [
"--python",
"3.12",
"finops-mcp==0.10.0"
]
}
}
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands, 2 hooks travel with it, and installing the plugin installs all of them — 96 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 17d ago Changed 2759784d9d66
- 18d ago Changed ce255a6150ee
- 20d ago Changed 9bd8257a7134
- 1mo ago Changed aed1642282dc
- 1mo ago First seen · 35 lines scan A 6cd497a2cd9e
nable is a plugin published in the GitHub repository getnable/finopsmcp (19 stars, last pushed 12d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
cloud-cost-agent
Native-first FinOps agent for AWS, GCP, and Azure. Finds cloud savings using each provider's own CLIs and recommendation engines (Cost Explorer/Compute Optimizer, GCP Recommender, Azure Advisor).
cloud-finops
Expert FinOps guidance for cloud, AI, SaaS, and data-platform spend (multi-provider, model-agnostic).
ai-platform-kit
Databricks platform engineering toolkit — provision workspaces, configure Unity Catalog, manage identity and governance, set up networking across Azure, AWS, and GCP.
azure-sdk-rust
Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs.
aws-agent-skills
Collection of AWS engineering skills for IAM, Lambda, DynamoDB, S3, and 14 other core AWS services.
azure-support-ticket
File and manage Azure support tickets from the terminal via the az CLI support extension.