Borrowing it
Nothing to install: this file belongs to opagani/cassini-workshop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/opagani/cassini-workshop/main/.claude/commands/git-remote.mdgit clone --depth 1 https://github.com/opagani/cassini-workshopWrote 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.
[](https://agentmods.dev/commands/opagani/cassini-workshop/git-remote)<a href="https://agentmods.dev/commands/opagani/cassini-workshop/git-remote"><img src="https://agentmods.dev/badge/commands/opagani/cassini-workshop/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.
<a href="https://agentmods.dev/commands/opagani/cassini-workshop/git-remote"><img src="https://agentmods.dev/badge/commands/opagani/cassini-workshop/git-remote.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 |
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.
This is a copy
100% identical to git-remote — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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— iforiginis set and points at github.com, stop and tell the user. Suggestgh repo vieworgh repo edit. gh auth status— refuse if not logged in. Tell the user to rungh auth login.- Read context:
CLAUDE.md,docs/PROJECT.md, existingREADME.md, anyLICENSE,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 statusshows 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/initstubTODO — one-line description.). - No installation, no usage, no example.
- Auto-generated
create-foo-appcontent untouched.
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
git-remote is a command published in the GitHub repository opagani/cassini-workshop (0 stars, last pushed 4mo 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. It is 100% identical to git-remote, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
customer-changelog-check
Audit whether user-visible changes in the current session have matching CHANGELOG.md entries; report MISSING with suggested lines; --fix auto-appends.
update-agentskills
Apply a reusable lesson to /.agentskills (rules/skills/templates/commands), backup + commit + push.
sync-claude
Update the vendored control plane + core commands in this repo to the latest heymegabyte/claude-bootstrap. Fires when the shared brain has moved on.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
speckit.git.validate
Validate current branch follows feature branch naming conventions.