add efficiency leaderboard metric#70
Open
kevinfosterNG wants to merge 1 commit into
Open
Conversation
|
@kevinfosterNG is attempting to deploy a commit to the sculpt Team on Vercel. A member of the Team first needs to authorize it. |
kevinfosterNG
marked this pull request as ready for review
June 17, 2026 15:23
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
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.
What changed
Efficiencytab to the homepage leaderboard besideCostandTokenstotalTokens / totalCostand display it as aTok/$columnWhy
The homepage currently highlights spend and token volume, but it does not surface which submissions get the most tokens per dollar. This adds a focused third ranking mode without changing the database schema.
Impact
Users can now switch the root leaderboard to an efficiency-oriented view and identify the most cost-efficient submissions, while existing cost and token rankings remain unchanged.
Validation
pnpm buildpnpm exec tsc --noEmitFails in the current repo due to pre-existing type/config issues unrelated to this change.
pnpm lintFails in the current repo because the script still uses
next lint, which is invalid under the current Next.js setup.pnpm testFails in the current repo because the script runs
nodedirectly ontest/ccusage.test.mts.