Add TOKEN_ECONOMY_GUIDANCE.md for budgeting AI spend and model choice#35
Open
awrobel-gd wants to merge 1 commit into
Open
Add TOKEN_ECONOMY_GUIDANCE.md for budgeting AI spend and model choice#35awrobel-gd wants to merge 1 commit into
awrobel-gd wants to merge 1 commit into
Conversation
… guidance - Introduced a new document detailing token economics and a repeatable budgeting model for AI spend. - Added a section on predicting monthly costs based on usage patterns and model choices. - Included a worked example to illustrate the budgeting process for engineers using AI in their development workflow.
awrobel-gd
force-pushed
the
token-economy-guidance
branch
from
a0dad5d to
270ae64
Compare
|
|
||
| | Component | Monthly range | What it is | | ||
| | --------------------------------- | ------------------- | -------------------------------------------------- | | ||
| | Baseline coding-agent usage (`B`) | ~$800 | PRs, refactors, reviews, day-to-day IDE agent work | |
Contributor
There was a problem hiding this comment.
IMHO Adam - I would NOT mix coding-agent usage and Specflow. I would only in this TOKEN Economy to show Specflow costs.
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
2 participants
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.
Introduced a new document detailing token economics and a repeatable budgeting model for AI spend.
Added a section on predicting monthly costs based on usage patterns and model choices.
Included a worked example to illustrate the budgeting process for engineers using AI in their development workflow.
more recommendation is needed — keep models in the same technology level (product generation), comparable LLM size and capabilities
Which models to use as LOW / MEDIUM / HIGH