A command for creating a GitHub remote repository for a project and preparing its basic public-facing files. It checks the current Git setup and guides choices such as the repository name, visibility, and license.

Use it when a local project needs a new GitHub repository. It helps set up the remote, README, license, contributing and security documents, and issue templates.

It helps avoid publishing an unfinished repository or overwriting existing project documentation. It also checks that no GitHub remote already exists and that the user is authenticated.

How robconery/kolea configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to robconery/kolea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/robconery/kolea/main/.claude/commands/git-remote.md

Clone the repo

git clone --depth 1 https://github.com/robconery/kolea

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/robconery/kolea/git-remote/github.svg)](https://agentmods.dev/commands/robconery/kolea/git-remote)

Your own site

<a href="https://agentmods.dev/commands/robconery/kolea/git-remote"><img src="https://agentmods.dev/badge/commands/robconery/kolea/git-remote/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/robconery/kolea/git-remote"><img src="https://agentmods.dev/badge/commands/robconery/kolea/git-remote.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,718 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.01718
Opus 5.5	$0.00011	$0.00687
Sonnet 5.5	$0.00006	$0.00344
Haiku 4.5	$0.00003	$0.00172

Measured 2mo ago against content hash 50341ffba673, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-remote scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

git-remote — 100% identical, 0 lines differ
git-remote — 100% identical, 0 lines differ

.claude/commands/git-remote.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

git-remote

Stand up the GitHub remote for this project and treat it like a calling card. A scrappy first-push leaves a scrappy first impression. Don't ship a stub. Use the github skill for any commit / PR work along the way.

Preflight

Refuse if a remote already exists. git remote -v — if origin is set and points at github.com, stop and tell the user. Suggest gh repo view or gh repo edit.
gh auth status — refuse if not logged in. Tell the user to run gh auth login.
Read context: CLAUDE.md, docs/PROJECT.md, existing README.md, any LICENSE, CONTRIBUTING.md, SECURITY.md, .github/ — never overwrite without consent.

Interview (ask in one batch)

Use AskUserQuestion to settle the choices that need a human:

Repo name — propose one derived from the project (CLAUDE.md / PROJECT.md), kebab-case, short. Offer 2–3 options.
Visibility — public, private. Default: public (it's a calling card).
License — propose one with a one-line rationale each:
- MIT — most permissive, easiest to adopt (Recommended for libs/tools).
- Apache-2.0 — same permissions + explicit patent grant; good for anything corporates will touch.
- AGPL-3.0 — strong copyleft; use when you want network-use modifications shared back.
- MPL-2.0 — file-level copyleft; middle ground.
- Unlicense / CC0 — public domain dedication. Recommend based on project type (CLI/lib → MIT; service/SaaS-y → Apache-2.0; opinionated stack you want kept open → AGPL).
Owner — personal account vs an org (only ask if gh auth status shows the user belongs to orgs).

Calling-card requirements (the bar)

The repo gets pushed only after all of these are in place:

README.md — must be real, never boilerplate

A boilerplate README is anything matching:

Just the project name and a one-liner.
Contains TODO, Lorem ipsum, "your project here", or the literal scaffold text (e.g. the /init stub TODO — one-line description.).
No installation, no usage, no example.
Auto-generated create-foo-app content untouched.

Read the full file on GitHub · 201 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 201 lines · 28 tokens per session scan A 50341ffba673

Subscribe to this mod's changes

git-remote is a command published in the GitHub repository robconery/kolea (11 stars, last pushed 28d ago), licensed MIT. It adds 28 tokens to every session and 1,718 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow cloudflare-d1 cloudflare-queues cloudflare-workers drizzle-orm email email-marketing

kolea: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

git-remote

Preflight

Interview (ask in one batch)

Calling-card requirements (the bar)

README.md — must be real, never boilerplate

What this file has done since we first saw it

Other commands, from other repositories

customer-changelog-check

retro

update-agentskills

rollback

sync-claude

worktree-create