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 agentmods add commands/mn-lizard-team/aiyu-multi-agent/finopsgit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/commands/mn-lizard-team/aiyu-multi-agent/finops)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/finops"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/finops.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00468 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
finops 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/finops
Cloud cost optimization, budget governance, and FinOps practices. Used when cloud bills are too high or when setting up cost accountability.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `finops-analyst`** | Skills: `clean-code, architecture, server-management`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Follow the task steps defined below
- Apply the Socratic Gate: ask clarifying questions if requirements are unclear
- Report completion status at the end
/finops — Cloud Cost Optimization
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `finops-analyst`** | Skills: `clean-code, architecture, server-management`
Task
Optimize cloud spending, identify waste, and implement cost governance.
Steps:
-
Cost Visibility
- Map current spending by service/team/environment
- Identify top cost drivers
- Check tagging coverage
-
Waste Identification
- Idle resources (unattached disks, stopped instances)
- Over-provisioned resources
- Old snapshots and unused storage
- Cross-region data transfer fees
-
Optimization Actions
- Right-size instances
- Purchase reserved/committed for steady workloads
- Schedule non-prod environments (off-hours shutdown)
- Implement lifecycle policies on storage
-
Governance Setup
- Budget alerts by team/environment
- Tagging policy enforcement
- Chargeback model design
- Cost anomaly detection
-
Reporting
- Monthly cost report
- Savings realized tracking
- Forecast vs actual
Usage Examples
/finops audit AWS spending this month
/finops identify wasted cloud resources
/finops right-size our EC2 instances
/finops set up budget alerts by team
/finops design chargeback model
/finops optimize storage costs
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.
- 5d ago First seen · 86 lines · 0 tokens per session scan A 53b81faa8bce
finops is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 468 tokens. 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-31.
Other commands, from other repositories
dashboard-server-tunnel-off
Disconnect the public tunnel. Usage /dashboard:server-tunnel-off.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
dashboard-server-config
Dashboard server config (secrets redacted). Runs locally, no LLM.
finops
Estimate and optimize cloud infrastructure costs. Usage - /mindforge:finops [service] [--forecast 6m] [--target-savings 20%].
dashboard-server-tunnel-on
Connect the public tunnel. Usage /dashboard:server-tunnel-on.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.