Skip to content

Add Token Battle to Community Projects #1387

Description

@tackeyy

What do you want to change?

I would like to add Token Battle to docs/guide/community-projects.md under Web Applications.

Proposed entry:

- [Token Battle](https://tokenbattle.vercel.app) - AI coding cost leaderboard for comparing monthly ccusage exports from Claude Code, Codex CLI, and Gemini CLI, with dashboard uploads, public rankings, and shareable profiles.

Why?

Token Battle uses ccusage monthly JSON exports as its ranking input, so it fits the Community Projects page. It is an independent web app and is not affiliated with ccusage.

How? (optional)

I can submit a one-line docs PR after approval. I previously opened #1386 directly before realizing new contributors need approval first, so I can reuse or resubmit that same small change if this looks acceptable.

Activity

  1. pullfrog commented on Jul 3, 2026

    @pullfrog
    Contributor
  2. github-actions commented on Jul 3, 2026

    @github-actions
    Contributor

    This issue was auto-closed. Issues from new contributors are auto-closed by default.

    Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.

    Keep the issue short, concrete, and written in your own voice.

    If a maintainer replies lgtmi, your future issues will stay open. If a maintainer replies lgtm, your future issues and PRs will stay open.

    See CONTRIBUTING.md.

  3. ryoppippi commented on Jul 3, 2026

    @ryoppippi
    Member

    lgtm

  4. github-actions commented on Jul 3, 2026

    @github-actions
    Contributor

    @tackeyy approved for issues and PRs. Your future issues and PRs will not be auto-closed.

    See CONTRIBUTING.md.

  5. ryoppippi commented on Aug 31, 2026

    @ryoppippi
    Member

    Historical audit: this discussion was auto-closed by the legacy contributor gate. That closure did not assess technical importance.

    Audit result: resolved. A later merged change or the current main implementation covers this request. This item is kept for history and does not need to be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    triage:resolvedResolved by a later change or current implementation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions