Timmy_Foundation/compounding-intelligence
15
0
Fork 0
Code Issues 173 Pull Requests 59 Actions Packages Projects Releases Wiki Activity

[ATLAS][Telemetry] Build local token and cost ingestion using Tokscale core patterns #229

New Issue
Open
opened 2026-04-22 04:57:31 +00:00 by Rockachopa · 0 comments
Rockachopa commented 2026-04-22 04:57:31 +00:00
Owner
Copy Link

Parent

Timmy_Foundation/hermes-agent#984

Source to Mine

  • junhoyeo/tokscale

What

Build a local-first telemetry ingestion layer that turns Hermes/agent session artifacts into normalized token and cost records without depending on a hosted dashboard.

Mine Tokscale core for:

  • unified usage schema
  • parser-per-client adapter model
  • cached pricing service with overrides and fallbacks

Tasks

  • Define a normalized schema for runs / sessions / messages with token and cost fields
  • Implement artifact parsers for Hermes output plus at least one second client/tool format
  • Add local pricing cache with override file and fallback behavior
  • Write rollups by model / provider / repo / agent / task
  • Document adapter contract for adding new parsers
  • Add fixture-backed ingestion tests

Acceptance Criteria

  • A normalized local schema exists for input/output/cache tokens and cost metadata
  • At least 2 ingestion adapters work end-to-end (Hermes + one other format)
  • Pricing can resolve from a local cache/override path without a mandatory hosted dependency
  • Rollups are emitted to a local report, DB, or artifact that can be consumed by the operator stack
  • Adapter interface is documented clearly enough for adding a third parser without guesswork
  • Fixture-backed tests prove ingestion and rollup correctness
## Parent Timmy_Foundation/hermes-agent#984 ## Source to Mine - `junhoyeo/tokscale` ## What Build a local-first telemetry ingestion layer that turns Hermes/agent session artifacts into normalized token and cost records without depending on a hosted dashboard. Mine Tokscale core for: - unified usage schema - parser-per-client adapter model - cached pricing service with overrides and fallbacks ## Tasks - [ ] Define a normalized schema for runs / sessions / messages with token and cost fields - [ ] Implement artifact parsers for Hermes output plus at least one second client/tool format - [ ] Add local pricing cache with override file and fallback behavior - [ ] Write rollups by model / provider / repo / agent / task - [ ] Document adapter contract for adding new parsers - [ ] Add fixture-backed ingestion tests ## Acceptance Criteria - [ ] A normalized local schema exists for input/output/cache tokens and cost metadata - [ ] At least 2 ingestion adapters work end-to-end (Hermes + one other format) - [ ] Pricing can resolve from a local cache/override path without a mandatory hosted dependency - [ ] Rollups are emitted to a local report, DB, or artifact that can be consumed by the operator stack - [ ] Adapter interface is documented clearly enough for adding a third parser without guesswork - [ ] Fixture-backed tests prove ingestion and rollup correctness
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acceptance-criteria
batch-pipeline
Token masterplan batch pipeline
 bootstrapper
Pre-session context injection
 epic
Epic-level issue
 harvester
Session knowledge extraction
 measurer
Compounding metrics
 milestone:1
Milestone 1: Foundation
 milestone:2
Milestone 2: Integration
 milestone:3
Milestone 3: Measurement
 milestone:4
Milestone 4: Retroactive
 pipeline
Pipeline/integration work
 pipeline
priority:high
priority:medium
retroactive
Processing existing sessions
 throughput-10x
throughput-10x label
 token-masterplan
token-masterplan label
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude codex-agent ezra gemini google grok hermes kimi manus perplexity
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/compounding-intelligence#229
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?