Pi coding agent extensions and skills by Vilosource — usage telemetry, internal tools, and shared infrastructure.
This is a monorepo. Each extension is published as its own scoped npm package under @vilosource/... and is independently installable. See docs/strategy/pi-extensions-monorepo-STRATEGY.md for why this repo exists and how it's organized.
| Package | Description | Status |
|---|---|---|
@vilosource/pi-usage-reporter |
Per-developer token usage and cost telemetry, shipped over OpenTelemetry to a centralized Grafana stack and Postgres-backed dashboard | Phase 0.1 spike shipped — emits real OTLP spans against the lab Collector; 42 tests pass; verified end-to-end with seeded dashboards. (DESIGN, research, decisions) |
(More to come.)
Each package can be installed individually from npm:
pi install npm:@vilosource/pi-usage-reporterOr, for a curated bundle of the whole repo:
pi install git:github.com/vilosource/pi-extensionsthen filter to the packages you want in ~/.pi/agent/settings.json per the Pi packages docs.
The dashboard that consumes OTel events from this extension lives in a separate repository: vilosource/agent-spend-dashboard. It is harness-agnostic — future Claude Code, Cursor, or Aider extensions emit the same agent.* attributes to the same dashboard. See docs/strategy/scope-and-deployment-STRATEGY.md for the three-artifact split.
Cross-cutting decisions that apply to every package in this repo.
| Doc | Subject |
|---|---|
scope-and-deployment-STRATEGY.md |
Three-artifact split (extension, reference dashboard server, organization deployments). Read this first. |
public-boundary-STRATEGY.md |
What may and may not appear in public artifacts; CI enforcement |
pi-extensions-monorepo-STRATEGY.md |
Why monorepo, why npm workspaces, naming conventions, tooling, release flow |
dashboard-backend-STRATEGY.md |
Reference dashboard server: Grafana + Postgres dual backend; phased delivery order |
architecture-PRINCIPLES.md |
What we believe about code quality and how it is mechanically enforced |
decisions-LOG.md |
Append-only log of small settled decisions |
Per-package design documents.
| Doc | Package |
|---|---|
pi-usage-reporter-DESIGN.md |
@vilosource/pi-usage-reporter |
Research briefs that informed the strategies and designs.
| Doc | Topic |
|---|---|
usage-tracking-dashboard-RESEARCH.md |
State of the art for tracking pi-mono token usage and shipping it to a multi-user dashboard |
All diagrams in this repo use Mermaid, rendered inline in Markdown. See AGENTS.md for the full convention.
See CONTRIBUTING.md. For agents (including AI agents) working in this repo, see AGENTS.md.
MIT — see LICENSE.