Integrations · Agents

Track what AI agents cost in GitHub Actions.

The GitHub Action reports what agents spend in CI, such as a pull request review bot. Its token entries arrive automatically, on the ticket of the pull request.

  • DoorThe GitHub Action
  • Brings inAutomatic token entries, submitted on arrival
  • Cost lands onThe pull request's ticket, or the project

One step after your agent.

The Action wraps the CLI. Add it after the step that runs your agent.

  1. 1

    Create a service token

    Create it in the web app under Settings. The person who creates it becomes the agent manager of everything the Action reports.

  2. 2

    Add the step

    Name the project, and pass the ticket when the job knows it. A passed ticket wins over every rule.

  3. 3

    Nothing to review

    Token entries from the Action arrive with the status submitted. They never go on a token sheet.

AgentAnswersTicketSummaryCostCI Review botMOSF-2Reviewed ranking PR$3.20CI Pen test agentASCP-1Pre-release pen test$12.47
Two agents that run in CI at the sample organization. Each has a person who answers for it.
# .github/workflows/review.yml, after the step that runs your agent - uses: tokencontroller/tokencontroller/packages/github-action@v1 with: project: storefront ticket: ${{ steps.plan.outputs.ticket }} # optional token: ${{ secrets.TOKEN_CONTROLLER_TOKEN }}

How CI cost is placed.

Reviews follow the pull request

A review of a pull request is placed on the ticket of that pull request.

The project wins over the repository

The Action names the project, and that wins over matching by repository.

Fallback to the project

CI work that matches no ticket lands on the project, never in a hidden bucket.

In the docs

Start alone in a few minutes. Add your team when the first month closes.

No card for the free plan. Fourteen days to try the Team plan.