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.
npx agentmods add skills/thermiteau/maverick/mav-git-workflownpx skills add thermiteau/maverick --skill mav-git-workflowgit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/skills/thermiteau/maverick/mav-git-workflow)<a href="https://agentmods.dev/skills/thermiteau/maverick/mav-git-workflow"><img src="https://agentmods.dev/badge/skills/thermiteau/maverick/mav-git-workflow.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.03748 |
| Opus 5 | $0.00025 | $0.01874 |
| Sonnet 5 | $0.00010 | $0.00750 |
| Haiku 4.5 | $0.00005 | $0.00375 |
Grade A, and why
mav-git-workflow 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 5d 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
A trunk-based strategy for all development work. This skill defines how branches, commits, and merges are managed.
Remote Repository Requirement
A configured remote repository is mandatory. Local-only git is a hard fail — all projects must push to a remote hosting service (GitHub, GitLab, Bitbucket, Azure Repos, etc.).
Validation
Before starting any work, verify a remote exists:
git remote -v
If no remote is configured:
- Stop work — do not proceed with feature branches, commits, or PRs
- Notify the user — report that no remote repository is configured and that this is a hard requirement
- Do not create a remote autonomously — the user must set up the remote repository and configure the origin
A project with no remote cannot use protected branches, pull requests, or CI/CD — all of which are foundational to this workflow.
Worktrees — required for multi-story workflows
Maverick's multi-story workflows (do-epic) run each story in
its own git worktree under .maverick/worktrees/. This keeps in-flight
stories isolated from each other and from the main checkout.
Worktree precondition
Before entering do-epic (or any flow that relies on
worktrees), verify the capability:
uv run maverick worktree list
If this fails, the workflow aborts with a hard error. Worktrees require:
- A non-shallow clone (
git rev-parse --is-shallow-repositoryreturnsfalse). Shallow clones cannot create new worktrees. - A git version that supports
git worktree add(2.15+). - Filesystem write access under
.maverick/worktrees/.
Worktree lifecycle
One worktree per story, created off the resolved base branch:
uv run maverick worktree create <branch> [--base <base-branch>]
On every exit path — merge, eject, abort — destroy the worktree:
uv run maverick worktree destroy <path>
Leaving stale worktrees inflates disk usage and confuses future
worktree list reads. The only reason to keep a worktree after exit is
if a PR was ejected and the human may want to inspect the in-flight
state — note the path in the eject comment.
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.
- 5d ago First seen · 447 lines · 50 tokens per session scan A 29d2d71227db
mav-git-workflow is a skill published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 3,748 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…