agent-cost-monitor

Monitor real-time token usage and estimated costs for ghostssh agent calls.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/sixscripts-ai/ghostssh --skill agent-cost-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-cost-monitor
Source: https://github.com/sixscripts-ai/ghostssh/tree/main/ghostssh-skills/agent-cost-monitor
Command: npx skills add https://github.com/sixscripts-ai/ghostssh --skill agent-cost-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track real-time token usage and estimated costs across all ghostssh agent calls, enabling cost-aware optimization and performance debugging.

Core Features & Use Cases

  • Real-time tracking of LLM invocations and estimated costs per session.
  • Centralized analytics via the agent_events Appwrite collection for reporting and capacity planning.
  • Generates usage reports and alerts to support cost governance and debugging.

Quick Start

Start the Cost Monitor in your GhostSSH environment to observe live token usage and costs across agent calls.

Frequently Asked Questions about agent-cost-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor real-time token usage and costs for LLM agent calls?

You can monitor real-time token usage by reading from the agent_events Appwrite collection, which computes per-session costs from metadata to provide live usage insights across multi-provider LLM workflows.

How does agent cost tracking work for multi-provider LLM workflows?

Agent cost tracking works by reading invocation metadata from the agent_events Appwrite collection and calculating per-session estimated costs, allowing you to analyze expenses across all ghostssh agent calls.

Can I use this for capacity planning across multi-provider LLM workflows?

Yes, you can use it for capacity planning. It centralizes analytics from the agent_events Appwrite collection, enabling you to review historical token usage and estimate future capacity needs across providers.

What's the best way to debug expensive LLM operations in a GhostSSH environment?

The best way to debug expensive operations is to start the cost monitor in your GhostSSH environment to observe live token usage and identify specific agent calls driving high estimated costs.

Do I need an Appwrite collection to track agent performance and costs?

Yes, you need the agent_events Appwrite collection. The cost monitor reads directly from this collection to compute per-session costs and expose usage insights for performance reviews.

Why are my estimated LLM costs higher than expected across agent sessions?

Estimated costs may be high due to expensive operations. Applying this cost monitor helps you review agent performance and debug specific sessions with excessive token usage from the agent_events data.