Langfuse was decommissioned on 2026-07-09 — do not add Langfuse tracing or query Langfuse for usage/cost. Use this skill only to learn where usage observability lives now. Token usage and cost questions route to `joelclaw usage` and ClickHouse otel_events.
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Langfuse is gone. It was never migrated to Flagg, its traces API 429'd/422'd under real query load (2026-07 backup/self-healing token-drain post-mortem), and every code path was removed from this repo (grep -ri langfuse packages/ apps/ returns zero).
joelclaw usage --hours 24 [--source router|agents|all] [--model X] [--machine Y] [--json]packages/system-bus/src/lib/clickhouse-usage-query.ts over ClickHouse joelclaw.otel_eventsmodel_router.result events carry a full usage object in metadata_json (fixed by passing --mode json to pi in inference.ts)packages/system-bus/src/lib/agent-usage/) parse Pi/Claude Code/Codex transcripts into agent_usage.turn events every 15 min (system/agent-usage.scan)packages/system-bus/src/lib/model-pricing.ts — provider-reported cost wins; OpenRouter public pricing is the benchmark fallback (pricing data only, never an inference path)daily-token-usage-report.ts reads ClickHouse directlypi/extensions/langfuse-cost still exists but degrades to disabled telemetry (fails soft, by design). Superseded by the agent-usage tailers; removal is a pending follow-up.LANGFUSE_* secrets in the secrets store are unused and can be revoked.Project receipts: .brain/projects/agent-usage-observability-2026-07-09.svx.
joelhooks/joelclaw
1fb2468
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.