The instrumented pipeline.
Anonymized, aggregate usage of opchain's own pipeline — which
skills actually run, what tier they run on, and what they cost.
Counts and sums only; no prompt content, no identity (see
privacy). Metered locally and opt-in by
oc-telemetry-ops, costed by oc-cost-ops.
Most-used skills
Buckets with fewer than 5 runs fold into other (k-anonymity).
Model-tier mix
- sonnet
- opus
- haiku
- fable
Tier, never the full model id — all the distribution needs.
Eval-score trend
Avg score across rubrics (oc-bug-check, oc-code-auditor, oc-prompt-ops), normalized 0–1.
Replays — real runs, with cost overlays
Pipeline runs recorded end-to-end, annotated with attributed spend + eval score.
Ship a RAG answer-bot
$9.12Discovery → vector-DB pack pick (pgvector) → retrieval eval goldset → staging → prod. Cost overlay shows spec on Opus, build on Sonnet, bulk embedding-eval batched.
Reverse-spec a Django monolith, ship a change
$5.7440k-line app, no docs → backfilled specs → one scoped feature → pre-commit gate → Render deploy. Most spend was the one-time reverse-spec sweep (Sonnet, high-throughput).
Build a triage agent on the Agent SDK
$11.38Subagent topology + tool budgets + a capped dedupe loop, gated on an agent eval goldset. Cost overlay flags the eval suite as the largest line — batched to halve it.
How this is measured
- Opt-in + local-first.
oc-telemetry-opsmeters runs to a local.checkpoints/usage.sqliteonly when enabled; default is off. - Content-free by schema. No prompt text, file paths, or identity is ever recorded — only categories and counts.
- Aggregate-only. Only this anonymized rollup leaves a machine; raw rows never do, and small cells fold into
other. - Cost is attributed, not estimated.
oc-cost-opsmultiplies measured tokens by the live price table.