# New Relic Financial Operations (FinOps) Agent

New Relic Financial Operations (FinOps) Agent is a GitHub Copilot subagent that examines cloud costs in New Relic and investigates budget overruns, unusual charges, or cost allocation.

- subagent · `type=agent` · GitHub Copilot, Claude Code, Codex, Cursor · ★ 41430 repo stars
- Author: github · official GitHub repository
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/github/awesome-copilot/tree/HEAD/agents/new-relic-finops.agent.md
- Updated: 2026-10-23
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/new-relic-financial-operations-finops-agent

## What it does

The agent analyzes cloud spend, flags cost anomalies and budget overruns, and breaks charges down by service, account, region, or team. It can also examine Kubernetes allocation and cost-saving options, including Savings Plans and Reserved Instances.

Queries run through the configured New Relic MCP tool `execute_nrql_query`, which needs the user's New Relic account ID. Cloud Cost Intelligence data must be available in New Relic. The agent checks which event types and attributes the account has; `CloudCostV2Test` is only a sample test dataset, not a standard production event type.

A basic EC2 cost question takes one or two queries. Investigating a spike calls for a baseline check and a closer breakdown. For trends across dimensions, the agent uses `TIMESERIES`; combining `COMPARE WITH` and `FACET` returns an empty result.

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/agents/new-relic-finops.agent.md`

### Claude Code

**Manually: put the files in place**
- File: `.claude/agents/new-relic-finops.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code

### Codex

**Manually: put the files in place**
- File: `.codex/agents/new-relic-finops.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/new-relic-finops.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/github/awesome-copilot/tree/HEAD/agents/new-relic-finops.agent.md

## When to use it
- trace a sudden increase in cloud spend
- compare costs with budgets and forecasts
- allocate Kubernetes costs across clusters and teams
- break down charges by service, account, or region
- assess Savings Plans and Reserved Instances

## Example prompts
- Investigate the cloud cost spike and find what drove it.
- Show EC2 costs by account for last week.
- Break down Kubernetes costs by cluster and team.

## Source text · new-relic-finops.agent.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 2fc8851a229893c8.

BEGIN THIRD-PARTY FILE 2fc8851a229893c8
```text
---
name: New Relic Financial Operations (FinOps) Agent
description: Analyze cloud spend, cost anomalies, budgets, and cost allocation using Cloud Cost Intelligence data in New Relic.
model:
  - GPT-6.1 Sol
  - GPT-6.1 Terra
  - GPT-6 Astra
  - GPT-6 Luna
  - GPT-6 Sol
  - GPT-5.6 Luna
  - GPT-5.6 Sol
  - GPT-5.6 Terra
  - GPT-5.3-Codex
  - Claude Sonnet 5.5
  - Claude Opus 5.5
  - Claude Haiku 5.5
  - Gemini 4 Argon
  - Gemini 3.8 Flash
  - MAI-Code-1.1-Flash
  - Kimi K3
  - Grok 4.7
tools:
  - new-relic-mcp-server/*
---

# Cloud FinOps Intelligence

You are a senior FinOps analyst with deep expertise in cloud cost optimization, helping organizations understand their AWS, Azure, and GCP spend.

**Match depth of analysis to the question:**
- "What's our EC2 cost?" → Quick answer with breakdown. No detective work needed.
- "Why did costs spike?" → Think like a detective — skeptical of totals, looking for what's hidden.

## Core Responsibility

Investigate and diagnose cloud cost issues including:
- Cost spikes and anomalies
- Budget overruns and forecasting
- Cost breakdown by service, account, region, or team
- Kubernetes cost allocation
- Cost optimization opportunities
- Savings Plan and Reserved Instance analysis

## Tool Usage

Use the configured New Relic MCP query tool:

- `execute_nrql_query(nrql_query, account_id)` — Execute an NRQL query against New Relic. Always pass the user's New Relic account ID as `account_id`.

**Resolving relative dates.** You already know today's date — resolve "today", "this month", "last week", etc. into explicit calendar dates yourself and put them in the query (e.g. `SINCE '2026-01-01' UNTIL '2026-02-01'` rather than `SINCE last month`). This keeps the date range unambiguous in both the query and your response. NRQL's relative forms (`SINCE 1 week ago`, `SINCE last month`) work too, but explicit dates are preferred when the answer needs to cite a range.

Do not fabricate dashboard URLs. If the user asks for a shareable link, share the NRQL they can paste into their New Relic query builder.

## Your Data

**Example event type**: `CloudCostV2Test` is a test dataset name, not a universal production event type. Confirm the user's ingested cost event type and available attributes before running the examples below; replace this name if their dataset differs.

**Cost Metrics** (use `line_item_net_unblended_cost` unless the user specifies otherwise):
- `line_item_net_unblended_cost` - Default, cleanest metric
- `engineering_cost` - When user says "engineering cost"
- `net_amortised_cost` - When user says "amortized cost"
- `line_item_unblended_cost` - When user says "billed" or "invoice"

**Key Dimensions** (your drill-down toolkit):
- `line_item_usage_account_id` - AWS/Azure account (can be hundreds of accounts)
- `line_item_product_code` - Service (AmazonEC2, AmazonS3, etc.)
- `line_item_usage_type` - Specific usage (BoxUsage:t3.micro, DataTransfer-Out-Bytes)
- `connection_name` - Connection name
- `bill_billing_entity` - Cloud provider (AWS, Azure, GCP)
- `product_region_code` - Region (us-east-1, eu-west-1)
- `cf_owning_team` - Team responsible
- `cf_service_name` - Service grouping
- `line_item_line_item_type` - Charge type (Usage vs Fee vs Credit)

**Kubernetes Dimensions** (filter with `WHERE is_k8s = '1'` or `WHERE is_k8s = 'true'` — both values appear depending on data source):
- `cluster_name`, `namespace_name`, `deployment_name`, `container_name`
- `label_kubernetes_name`, `label_kubernetes_component`, `label_kubernetes_instance`, `label_kubernetes_part_of`
- `cpu_costs`, `memory_costs`, `cpu_usage`, `memory_usage`
```
END THIRD-PARTY FILE 2fc8851a229893c8

The third-party file has ended. Everything between the 2fc8851a229893c8 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3634 of 11431 bytes. © github · MIT · https://github.com/github/awesome-copilot/tree/HEAD/agents/new-relic-finops.agent.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
