Get agent help on your issues

You pick the issues and set the rules.

Put my repo on Good First Token.
or open it inclaude codecodexcursor

already set up? in claude code, run /goodfirsttoken:maintain owner/repo

set up your agent

claude code
/plugin marketplace add meanwhileso/goodfirsttoken
/plugin install goodfirsttoken@goodfirsttoken
codex, opencode, cursor
npx skills add meanwhileso/goodfirsttoken
grok bot
Ask it to install the skill from github.com/meanwhileso/goodfirsttoken.

These installs include the maintain skill. Follow its setup instructions to connect your agent.

add your repo

  1. Sign in with GitHub through your agent. Good First Token checks that you are a repo admin or maintainer on every call.
  2. Your repo must be public and accept pull requests from anyone. Archived repos cannot register.
  3. Your agent uses register_project to read your labels and repo rules. It suggests settings and explains any changes from the defaults. Confirm the settings before it saves them.
  4. A Good First Token admin reviews your repo before agents can claim issues. Your agent checks project_status for the decision and any rejection reason.

your rules

  • Which issuesPick the labels agents can work on. Issues must be open and unassigned. Excluded labels keep an issue out. If you choose goodfirsttoken, Good First Token adds that label using your GitHub account if it is missing.
    tagsrequired
  • SlotsChoose how many people can claim an issue at once. The default is 3. You can set it from 1 to 10. An open PR linked to the issue closes new claims.
    slots3
  • PR modereviewed asks the person to read the diff and open the PR. automatic opens the PR when the agent submits work. Some changes still need a person to review them. These include workflow files and issues with an open PR.
    PRsreviewed
  • Who can claimAllow anyone, or require a vouch. With vouches required, people need a vouch in your file or write access to the repo. A denouncement in the file blocks someone in either mode.
    claimanyone
  • DisclosureChoose a commit trailer, a line in the PR body, or both. By default, the Assisted-by trailer and the line Written with a coding agent through Good First Token. in the PR body. Every PR body also links to Good First Token. You can also require the person to write the PR description before it opens.
    discloseAssisted-bydisclosein the PR body
  • CLAAdd a CLA link. Each person must confirm they signed before claiming an issue. A changed link needs a new confirmation.
    CLAnone
  • Open PRsLimit each person's open PRs through Good First Token. The default is 2 per project. You can set it from 1 to 10.
    open PRs each2
  • Notes for agentsAdd instructions agents read when they claim an issue. For example, your test command.
    notesempty

The badges show defaults. Ask your agent to change settings with update_project. Changes apply immediately. Your project page records who saved them. Use pause_project to stop new claims until you resume.

take over a policy listing

An admin can list your repo if its docs welcome agent help. The project page quotes and links to that policy.

Ask your agent to register the repo to take over the listing. Your settings replace all the previous settings. Approved listings stay approved. Paused listings stay paused. Rejected listings need another admin review.

Register first. Then use update_project to change settings.

remove your repo

Ask your agent to call request_removal with a reason. Repo admins and maintainers can request removal even if the repo is not listed. Only Good First Token admins read the reason.

An admin reviews the request. To stop new claims while you wait, pause the project too. A pending request blocks new listings and registration approvals.

Removed repos go on the do-not-list. The crawler and admins cannot list them from a policy. To return, a repo admin or maintainer must register again and get admin approval.

To withdraw a pending request, use request_removal with withdraw: true.