Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/fmflurry/settings-opencodeWrote 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/fmflurry/settings-opencode/git)<a href="https://agentmods.dev/commands/fmflurry/settings-opencode/git"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/git/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/fmflurry/settings-opencode/git"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/git.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.00010 | $0.00593 |
| Opus 5.5 | $0.00004 | $0.00237 |
| Sonnet 5.5 | $0.00002 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
git 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 26d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Command
Handle this git task: $ARGUMENTS
Route to the
git-specialistagent when available. For richer flows, prefer the existing/push-changesor/create-pull-requestcommands.
Requirements
- Enforce the commit format exactly:
<type>(<scope>): <short summary>
[optional body]
[optional footer(s)]
If scope is not useful or not clear, this form is also valid:
<type>: <short summary>
Allowed types: feat, fix, docs, style, refactor, test, chore
English only: commit messages MUST be written in English — subject, body, and footers — even when the user or conversation is French. Translate French input into an English summary; never emit French commit messages.
- Enforce the branch naming format exactly:
<type>/<scope>-<short-description>
scope is required for branches. If it is ambiguous, ask one short question via AskUserQuestion before creating the branch.
scope must be a single lowercase token with letters and numbers only. The first - after / separates scope from short-description.
- Workflow:
- inspect repository state first (
git status,git diff,git log --oneline -5) - use a compliant branch name for branch operations
- use a compliant conventional commit message for commit operations
- stage only relevant changes (avoid
git add -A/git add .) - never commit files that may contain secrets (
.env,*credentials*,*.key,*.pem) - avoid destructive commands unless explicitly requested
- for pull request tasks: detect host from
git remote get-url origin— useghfor GitHub,az repos prfor Azure DevOps (dev.azure.com/visualstudio.com). Stop if unknown. Return the PR URL. - Azure DevOps PR defaults: reviewers =
PIXELS, no--draft. Title must follow conventional commit format. - use the repository default branch as PR base when available, otherwise prefer
main, thenmaster - return an existing PR URL instead of creating a duplicate PR for the same branch
- never use
--no-verifyor skip hooks unless the user explicitly asks - never amend or force-push without explicit user authorization
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.
- 26d ago Changed · +2 lines e994970e9ae5
- 1mo ago First seen · 63 lines · 10 tokens per session scan A a685c8294451
git is a command published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 593 once invoked, about $0.0000 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.
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.
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.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.