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 skills add OutlineDriven/odin-codex-plugin --skill git-branchlessgit clone --depth 1 https://github.com/OutlineDriven/odin-codex-pluginWrote 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/outlinedriven/odin-codex-plugin/git-branchless)<a href="https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/git-branchless"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/git-branchless/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/skills/outlinedriven/odin-codex-plugin/git-branchless"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/git-branchless.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.00131 | $0.01828 |
| Opus 5.5 | $0.00052 | $0.00731 |
| Sonnet 5.5 | $0.00026 | $0.00366 |
| Haiku 4.5 | $0.00013 | $0.00183 |
Grade A, and why
git-branchless 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- git-branchless — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git-branchless
Branchless treats commits as checkpoints, detached HEAD as the default work mode, and branches as publishing artifacts. This skill enforces that mental model and routes every common git workflow to its branchless equivalent. Reference docs:
references/commands.md— every command, flag, revset, config key.references/recipes.md— concrete sequences + decision rubric.references/recovery.md— undo, restack, hide, snapshot, GC semantics.
Pre-flight gate [LOAD-BEARING]
Before applying any rule below, confirm branchless is initialized for the current repository. Run:
test -d "$(git rev-parse --git-common-dir)/branchless" && git config --get branchless.core.mainBranch
(Resolving the git-common-dir handles linked worktrees, where .git is a
file rather than a directory and branchless state lives in the main repo's
git dir.)
| Result | Skill behavior |
|---|---|
| Both succeed | Skill is active. Apply the rules below. Acknowledge with one line: git-branchless active — main=<value>. |
| Either fails | Skill is silently inert. Emit one line: git-branchless not initialized; skill inactive. Yield to plain git. Do not suggest git branchless init unless the user explicitly asks how to enable. |
The inert path is intentional. This skill does not nag and does not refuse legitimate work in repos where branchless was never adopted.
Always / Never (operation-class framing)
Each rule names an operation class, not a command. Plain-git commands are fine when they fall outside the class.
| Class | Always | Never |
|---|---|---|
| Stack edits (reorder, fixup, squash, split) | git move, git move -F, git reword, and git split where available [v0.11.0+] (use the Recipe 4 workaround on older versions). |
git rebase -i to drive stack edits. |
| Base updates (rebase a stack onto fresh main) | git sync --pull (or git move -b 'stack()' -d origin/main). Read the skip summary. |
git pull --rebase against a stack. |
| Undoing committed history | git undo -i. |
git reset --hard <SHA> against any commit you have already made. |
| Discarding local work in progress | git hide -r <tip> (recoverable). |
git branch -D or git reset --hard purely to wipe. |
| Branch creation for ephemeral work | Detached HEAD until publish; commit immediately, branch later. | git checkout -b feature/X before the first commit exists. |
| Publishing | Branch the tip then git push -u, or git submit -c on supported forges. |
Force-push as a way to "fix" your local history. |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 141 lines · 131 tokens per session scan A 4721acdd7e87
git-branchless is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (14 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 131 tokens to every session and 1,828 once invoked, about $0.0005 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 skills, from other repositories
git-guardrails-claude-code
Install a Claude-Code PreToolUse hook that blocks destructive git commands (push variants including force-push, hard reset, force clean, branch -D, checkout/restore overwrites) before Bash runs them. Use when the user wants git safety rails, force-push prevention, or repository-wipe protection.
git-branchless
Enforce idiomatic git-branchless during planning and executing tasks — detached-HEAD-first work, in-memory rebase via git move, event-log recovery via git undo, deferred branch creation, speculative-merge git sync for base updates. Use when planning or executing multi-commit work, history rewrites, stack edits…
tidy
Tidy-operations dispatcher. Invoke on "tidy", "clean up", "tidy this file/memory/workspace/git/docs", or when active context (current file, diff, stack, memory directory) has structural rot to resolve before touching behavior. Detects target domain from context and routes to the sibling skill. Requires explicit target…
request-refactor-plan
Plan a refactor as a sequence of tiny, working commits via adversarial interview. Default output is a markdown plan at /docs/refactor-plans/ .md; pass --emit-issue to also file a GitHub issue. Trigger on structural refactors (rename, extract, move, split, dedupe) — NOT new features.
setup-gitignore
Initialize or idempotently revise the repo's .gitignore by composing gitignore.io templates, AI-tooling/IDE patterns, and confirmed noise from git status. Use when the user says "set up gitignore", "fix gitignore", or untracked files keep appearing in git status.
setup-pre-commit
Install git pre-commit hooks via the project's hook tool — Husky+lint-staged (JS), pre-commit (Python/OCaml), lefthook (Go), cargo-husky (Rust). Use when the user wants commit-time formatting, linting, type-checking, or test gates. Detects ecosystem first.