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 niels-emmer/myace --skill git-workflowgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/git-workflow)<a href="https://agentmods.dev/skills/niels-emmer/myace/git-workflow"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/git-workflow/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/niels-emmer/myace/git-workflow"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/git-workflow.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.00024 | $0.00722 |
| Opus 5 | $0.00012 | $0.00361 |
| Sonnet 5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
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 9d 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.
Purpose
Keep git usage simple enough that it never gets in the way of moving fast, while still leaving a clean, readable history and a clear signal for when something needs a second look.
When to use it
Any time you're starting new work, deciding whether to branch, or deciding whether a change needs a pull request versus just landing directly.
Branch naming
Use a short prefix that says what kind of change it is, then a few words describing it, separated by hyphens:
feat/short-description— new functionalityfix/short-description— bug fixchore/short-description— maintenance, deps, config, cleanupdocs/short-description— documentation only
Keep the branch name short enough to read in a terminal prompt. If the work doesn't fit cleanly into one of these, feat/ is a safe default.
Commit messages
Write each commit as a small, coherent unit with a message that states what changed and why. Use a conventional prefix so the history is scannable:
feat:— new functionalityfix:— bug fixchore:— maintenance, deps, config, cleanupdocs:— documentation only
Keep the subject under ~50 characters and imperative ("add retry to the fetch", not "added retry"). If the "why" isn't obvious from the diff, add a short body paragraph — the message should make the intent recoverable later, not just describe the diff.
When to open a PR vs. just push
For solo or low-stakes prototype work on your own feature branch, it's fine to push directly and merge without ceremony — a PR that nobody else will read doesn't add safety, it just adds a click.
Open a real pull request (even solo) when:
- The change touches shared/production infrastructure, data migrations, or anything hard to undo.
- You want a second pass before it lands — e.g. you're not fully confident in the approach.
- Other people are working in the same repo and need visibility before it merges.
- The default/main branch is protected and requires one anyway.
Otherwise, commit on the feature branch and merge or push straight to the target branch once it works.
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.
- 9d ago First seen · 65 lines · 24 tokens per session scan A 338177aff41d
Git Workflow is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 722 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.
loom-git-workflow
Git operations guidance including branching strategies, commit conventions, merge workflows, conflict resolution, and worktree management.
dependabot
Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update…
commit-message-storyteller
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this"…
conventional-commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis.