Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. 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/friedbotstudio/baseline/main/.claude/commands/grant-push.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/grant-push)<a href="https://agentmods.dev/commands/friedbotstudio/baseline/grant-push"><img src="https://agentmods.dev/badge/commands/friedbotstudio/baseline/grant-push/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/friedbotstudio/baseline/grant-push"><img src="https://agentmods.dev/badge/commands/friedbotstudio/baseline/grant-push.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.00027 | $0.00667 |
| Opus 5.5 | $0.00011 | $0.00267 |
| Sonnet 5.5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
grant-push 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 1mo 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.
What it actually says
Write a consent token to .claude/state/push_consent so the Git Commit Guard hook allows the next git push on a protected branch. The token is the current UNIX epoch timestamp on line 1; any optional note goes on line 2.
How this works structurally: when the user typed /grant-push, the consent_gate_grant UserPromptSubmit hook ran before this body was passed to Claude and wrote a short-lived consent marker at .claude/state/.push_consent_grant. The git_commit_guard PreToolUse hook (Write matcher) reads that marker and allows Claude to write the consent file because the marker is fresh. Claude cannot forge the marker — that's what makes the gate structural. The Bash-matcher leg of the same guard then enforces the consent token on the actual git push invocation, but only when the current branch matches project.json → git.protected_branches.
State-write discipline (binding — see .claude/CONSTITUTION.md §2 "State-write discipline"). The consent token at .claude/state/push_consent is a Tier 1 consent artifact: it SHALL be written with the Write tool only. You SHALL NOT write it via Bash (no >/>> redirect, heredoc, tee, cp, or sed -i) — destructive_cmd_guard blocks Bash writes to consent paths, and the git_commit_guard Write matcher validates the marker only on the Write tool. Use Bash solely for the precheck (git rev-parse) and the epoch (date +%s).
Steps:
- Git-repo precheck. Run
git rev-parse --is-inside-work-tree 2>/dev/null. If the exit status is non-zero, this project is not a git repository: refuse to write the consent token and tell the user "Not a git repository —/grant-pushis inapplicable. Push has no meaning outside a git repo." Stop here. - Run
date +%sto get the current epoch. - Write the consent token with the Write tool, overwriting any prior token: the epoch on line 1 (and the optional note
$ARGUMENTSon line 2 if non-empty) to.claude/state/push_consent. Do not use a Bash redirect ortee— that path is guard-blocked. - Confirm to the user: "Push consent granted at , valid for 300s (until <HH:MM:SS local>). The next
git pushon a protected branch will be allowed. Pushes on branches NOT inproject.json → git.protected_branchesdo not require this consent."
Do not run git push yourself in this command. The user asks explicitly when they want a push; this command only opens the window.
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.
- 1mo ago First seen · 22 lines · 27 tokens per session scan A ede000e21619
grant-push is a command published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 27 tokens to every session and 667 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-30.
Other commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
standup
Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.
sprint
Run an autonomous sprint from maintained specs and plans, with truthful verification and no duplicate artifact approval ceremonies.