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 fmind/dot --skill git-deliverygit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/git-delivery)<a href="https://agentmods.dev/skills/fmind/dot/git-delivery"><img src="https://agentmods.dev/badge/skills/fmind/dot/git-delivery/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/fmind/dot/git-delivery"><img src="https://agentmods.dev/badge/skills/fmind/dot/git-delivery.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.00023 | $0.00402 |
| Opus 5.5 | $0.00009 | $0.00161 |
| Sonnet 5.5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
git-delivery 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 4d 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
Git Delivery
Deliver only the authorized changes while preserving the index, branch intent, and enabled hooks. Branching, pushing, and release publication are separate modes of the same workflow.
Workflow
- Resolve delivery authority and target branch: take both from the request; inspect the current branch and unmerged work before switching. Never overwrite an existing branch or move unrelated commits.
- Match work to the request: a commit-only request preserves the staged selection and stops after committing. A delivery request includes staging and pushing only its intended changes; neither implies release publication.
- Follow requested branch and release modes: if the user requests a branch or PR, follow git-worktree and github-pull-request. A later release instruction selects the release mode; use the repository's native release task where present.
- Verify the delivery: the exact commit, remote destination, and requested publication level. Keep published tags immutable and preserve enabled hooks.
Task guides
- conventional-commit: Commit the staged selection with Conventional Commits.
- git-add-commit-push: Stage, commit, push, and recover hook failures within the authorized scope.
- release: Prepare, publish when requested, or verify versioned releases.
What ships with it
7 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.
- references/conventional-commit.md 2.0 KB
- references/git-add-commit-push.md 3.0 KB
- references/release/GUIDE.md 2.5 KB
- references/release/references/publish.md 4.0 KB
- references/release/references/verify-assets.md 1.4 KB
- references/release/references/verify.md 2.2 KB
- references/release/references/versioning.md 1.1 KB
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.
- 4d ago Changed d5f486df6229
- 9d ago Changed 11085549a349
- 11d ago Changed 10aa4b21632f
- 12d ago Changed · -1 tokens per session a727b0cc19fa
- 14d ago Changed deadd2be31e2
- 20d ago Changed 62d12f371508
- 26d ago Changed 64a9da05e36f
- 29d ago First seen · 33 lines · 24 tokens per session scan A fedeb194fdd9
git-delivery is a skill published in the GitHub repository fmind/dot (11 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 402 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-09-17.
Other skills, from other repositories
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
git-add-commit-push
Stage, commit (Conventional Commits), and push in one flow, auto-healing lefthook pre-commit and pre-push failures. Use when committing and pushing work end-to-end.
lefthook
Canonical lefthook git-hooks setup — pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use when configuring or debugging git hooks.
conventional-commit
Write a Conventional Commits subject for the staged changes and commit them. Use when committing staged work with a typed, scoped message.
commit
Describe and finalize work with jj-vcs — drafting a description for the current change, splitting mixed work into focused commits, and advancing to a clean working copy. Use when asked to commit, when finishing a unit of work, or when starting new work on top of undescribed changes.
github-workflow
Professional GitHub issue/PR workflow with gh CLI. Use when a best-practice use case needs issue → PR → Closes.