Starter kit: a GitHub coding agent that can't merge without you

A public repo where a coding agent turns GitHub issues into pull requests with a plan, checks and screenshots, and only a person merges. No API key, a US$20 monthly cap. Members also get the sign-off sheet for whoever approves the agent.

At a glance

You get: a repo where an agent turns issues into pull requests
API keys stored: 0 · Monthly cap: US$20 · Licence: MIT
Try it now: 3 requests a day, no rights in the repo needed

Start the issue with @claude. Paste this one or write your own:

@claude add a dark mode that follows the system setting

Before you sign in

Your account must be at least 30 days old. The sign-in reads only your public profile and stores your username, its numeric id, the date the account was created and the date you signed up.

Get a pull request in minutes, and keep the merge

Every change the agent makes stops at your review.
Every change the agent makes stops at your review.

Write @claude in a GitHub issue, and a few minutes later a pull request arrives with the plan, the check results and before and after screenshots. You review it and merge; nothing reaches main before that. The agent runs in GitHub Actions with no API key and a read-only token, on a Claude Console workspace capped at US$20 a month.

Copy it into your own repo, MIT licensed

gh repo create my-agent-repo \
  --template florezflow/governed-agent-starter \
  --public --clone

The copy holds the files only. The README's setup adds the ruleset, the label and the variables, and the use case covers the Claude Console side. What you get:

  • .github/workflows/claude.yml: the three jobs, gate, agent and deliver
  • .github/rulesets/main.json: pull requests only, code owner review, design check required
  • AGENTS.md and CLAUDE.md: the agent's rules
  • .claude/settings.json: allowed tools, and deny rules so the agent can't edit its guardrails
  • .github/ISSUE_TEMPLATE/: the issue form

Members get what helps you roll it out

  • The sign-off sheet: 12 checks, each a yes or a no, for the lead or security reviewer who approves an agent on a repository.
  • New use cases by email as I write them, kept current.

The rest of this page is free for members. Enter your email, and the link in it signs you in.