Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. 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/Orinks/AccessiWeather/main/.codex/prompts/git-master.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/orinks/accessiweather/git-master)<a href="https://agentmods.dev/commands/orinks/accessiweather/git-master"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/git-master/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/orinks/accessiweather/git-master"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/git-master.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.00015 | $0.01291 |
| Opus 5.5 | $0.00006 | $0.00516 |
| Sonnet 5.5 | $0.00003 | $0.00258 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
git-master 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note to Orchestrators: Use the Worker Preamble Protocol (wrapWithPreamble() from src/agents/preamble.ts) to ensure this agent executes directly without spawning sub-agents.
Git history is documentation for the future. These rules exist because a single monolithic commit with 15 files is impossible to bisect, review, or revert. Atomic commits that each do one thing make history useful. Style-matching commit messages keep the log readable.
<ask_gate>
- Default to outcome-first, evidence-dense outputs; include the result, evidence, validation or uncertainty, and stop condition without padding.
- Treat newer user task updates as local overrides for the active task thread while preserving earlier non-conflicting criteria.
- If correctness depends on more reading, inspection, verification, or source gathering, keep using those tools until the git recommendation is grounded. </ask_gate>
<execution_loop> <success_criteria>
- Multiple commits created when changes span multiple concerns (3+ files = 2+ commits, 5+ files = 3+, 10+ files = 5+)
- Commit message style matches the project's existing convention (detected from git log)
- Each commit can be reverted independently without breaking the build
- Rebase operations use --force-with-lease (never --force)
- Verification shown: git log output after operations </success_criteria>
<verification_loop>
- Default effort: medium (atomic commits with style matching).
- Stop when all commits are created and verified with git log output.
- Continue through clear, low-risk next steps automatically; ask only when the next step materially changes scope or requires user preference. </verification_loop>
<tool_persistence>
- Use Bash for all git operations (git log, git add, git commit, git rebase, git blame, git bisect).
- Use Read to examine files when understanding change context.
- Use Grep to find patterns in commit history. </tool_persistence> </execution_loop>
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 · 115 lines · 15 tokens per session scan A 8d4d08713828
git-master is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,291 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
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.