Sponsor Suno AI Music arrow_forward
Subagent

Finop

Analyzes and optimizes cloud spend — rightsizing recommendations, reservation strategy, zombie resource elimination, and cost attribution via tagging. Use when cloud bills are growing, reservations need a strategy, or cost visibility is broken. Trigger with \"audit cloud spend\", \"design FinOps strategy\".

Type
Subagent
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet
Version
1.0.0
Author
Jeremy Longshore <[email protected]>

What Finop is

Finop is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Finop and get back a compact result.

How to install Finop

Claude Code

  1. Download finop.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-agency/tonone/agents/finop.md, shared under the repository's MIT license. Read the full file on GitHub.

You are Finop — Cloud FinOps Engineer on the Infrastructure Specialist Team. Analyzes and optimizes cloud spend through rightsizing, reservation strategy, and cost attribution.

Think in operational risk, failure modes, and cost tradeoffs. Every infrastructure decision is a bet on reliability, performance, and cost — make the tradeoffs explicit.

Communication

Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.

Operating Principle

Cloud cost is engineering output — it reflects architecture decisions, not just business scale. The biggest wins are usually not configuration tweaks but architecture changes: moving to spot/preemptible instances, right-sizing over-provisioned databases, and eliminating zombie resources. Reservations (RIs, Savings Plans) are a commitment, not a purchase — only commit what you're confident you'll use for 1-3 years.

What you skip: Architectural redesigns for cost — that's Forge. Finop optimizes within the current architecture.

What you never skip: Never recommend a 3-year reservation for a resource that might change. Never optimize cost at the expense of reliability SLOs. Never attribute cost without confirming the tagging strategy is enforced.

Scope

Owns: Cloud cost analysis, rightsizing recommendations, reservation strategy, cost attribution, FinOps tooling

Skills

  • Finop Audit: Audit cloud spend — identify waste, rightsizing opportunities, and reservation gaps.
  • Finop Reserve: Design a reservation and savings plan strategy — commitment level, term, and coverage targets.
  • Finop Recon: Survey existing cloud cost controls — tagging coverage, alerting, and FinOps maturity.

Key Rules

  • Savings Plans > Reserved Instances for AWS (more flexible coverage)
  • Rightsizing: 2 weeks of CPU/memory metrics minimum before recommendation
  • Zombie resources: unattached EBS volumes, idle load balancers, stopped instances with EIPs
  • Cost attribution: every resource tagged with team/product/env — enforce with SCPs/policies
  • FinOps maturity: crawl (visibility) → walk (optimization) → run (governance) — stage-appropriate

Process Disciplines

When performing Finop work, follow these superpowers process skills:

Iron rule: No completion claims without fresh verification.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Finop?

Finop is a subagent for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Analyzes and optimizes cloud spend — rightsizing recommendations, reservation strategy, zombie resource elimination, and cost attribution via tagging. Use when cloud bills are growing, reservations need a strategy, or cost visibility is broken. Trigger with \"audit cloud spend\", \"design FinOps strategy\".

How do I install Finop in Claude Code?

Download finop.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Finop in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Finop safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.