weave-cost

Track AI token usage and costs for Elastic demos.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ajmeyers42/loom --skill weave-cost
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weave-cost
Source: https://github.com/ajmeyers42/loom/tree/main/skills/weave-cost
Command: npx skills add https://github.com/ajmeyers42/loom --skill weave-cost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-dimensional token visibility and cost transparency for Elastic demos, enabling the SA to track Claude Code / Cursor usage and provide customers with an AI Cost + Usage view when Agent Builder is involved.

Core Features & Use Cases

  • SA tooling: session-level token tracking, cost dashboards, and usage metrics to improve governance during builds.
  • Demo feature: adds an AI Cost + Usage dashboard to demos that include Elastic Agent Builder, enabling visibility into AI spend.
  • Integration guidance: index naming, schema references, seed data guidance, ILM policy, and dashboard templates to support end-to-end demos.

Quick Start

Enable token visibility in the engagement by including weave-cost flow and ensuring seed data and dashboards are set up.

Frequently Asked Questions about weave-cost

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

FAQPage Schema
How do I track AI token usage and cost in Elastic Agent Builder demos?▼

Show AI token spend in Kibana dashboards by configuring an agent-sessions index schema, loading seed data, applying an ILM policy, and deploying a dashboard plan. This provides per-session token tracking and cost transparency.

What is per-session token tracking for Elastic demos?▼

Per-session token tracking is a method to monitor AI token spend and usage metrics during Elastic Agent Builder engagements. It provides cost transparency through dedicated Kibana dashboards for SA tooling and customer visibility.

Do I need an ILM policy to set up cost tracking dashboards in Kibana?▼

Yes, an ILM policy is required to manage the agent-sessions index lifecycle. The setup also requires a specific index schema, seed data, and a Kibana dashboard plan to properly display AI cost and usage metrics.

Can I use this to monitor Claude Code or Cursor usage during build sessions?▼

Yes, you can monitor Claude Code and Cursor usage during build sessions. It enables SA tooling to track session-level token consumption and generate cost dashboards for governance.

What schema and data are needed to enable token visibility in Elastic?▼

Token visibility requires an agent-sessions index schema, seed data for initialization, an ILM policy for data retention, and an aligned Kibana dashboard plan to visualize the AI cost and usage metrics.

When should I add an AI cost and usage dashboard to my Elastic demo?▼

Add an AI cost and usage dashboard whenever a demo includes Elastic Agent Builder or other AI components. This provides customers with visibility into AI spend and improves governance during builds.