Add cost-tracker workflow for agent spend observability#319
Open
adamhenson wants to merge 3 commits intogithubnext:mainfrom
Open
Add cost-tracker workflow for agent spend observability#319adamhenson wants to merge 3 commits intogithubnext:mainfrom
adamhenson wants to merge 3 commits intogithubnext:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
workflows/cost-tracker.md— fires onworkflow_run: completed, downloads theagent-artifactsartifact written by gh-aw's firewall, parsestoken-usage.jsonl, calculates per-model cost, and posts a spend summary on the associated pull request or creates a cost report issue when no PR is founddocs/cost-tracker.md— installation instructions, mermaid flow diagram, and configuration guide (modelled afterdocs/ci-doctor.md)README.md— add Cost Tracker to the Fault Analysis Workflows sectionCloses #315. Related to #297.
Notes
agent-artifactsartifact exists the workflow produces no outputtoken-usage.jsonlwritten by gh-aw's firewall — no extra setup needed beyond enabling the firewall (the default)