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/ericrisco/rsc-harness/git-workflownpx skills add ericrisco/rsc-harness --skill git-workflowgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/git-workflow)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/git-workflow"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/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.00127 | $0.03229 |
| Opus 5 | $0.00063 | $0.01614 |
| Sonnet 5 | $0.00025 | $0.00646 |
| Haiku 4.5 | $0.00013 | $0.00323 |
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 today.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-workflow — the grammar and hygiene of version control
Git history is a message to the next human who reads git log, runs git blame on a broken line,
or bisects a regression at 2am. That human is usually future-you. Every rule in this skill exists
to make the next reader's job faster, not to make this moment cheaper. A repo with legible branch
names, conventional commits, and a clean linear narrative is a repo you can reason about; a repo with
wip, fix stuff, and force-pushed shared history is one you fight.
This is the portable convention layer. It is independent of any SDD phase or CI platform — it is
the grammar that ../ship/SKILL.md, ../worktrees/SKILL.md, and ../deployment/SKILL.md all lean on.
It does not decide whether to land the work (that is ship) and it does not automate releases in a
pipeline (that is deployment). It tells you how to name, commit, untangle, and tag — correctly.
Branch naming
Name a branch from its intent, prefixed by its kind, as a kebab-case slug. Keep it short-lived:
hours to days, not weeks. Long branches drift from main and turn into merge pain.
| Prefix | Use for | Why |
|---|---|---|
feat/ |
a new capability | matches the feat commit type; signals a MINOR |
fix/ |
a bug fix | matches fix; signals a PATCH |
hotfix/ |
an urgent fix landing straight to production | flags "skip the slow path" to reviewers |
chore/ |
tooling, deps, config — no product behavior | keeps non-feature noise out of the feature log |
docs/ |
documentation only | reviewers can fast-track, no test gate needed |
refactor/ |
restructure without behavior change | sets the expectation: tests stay green, no new behavior |
What ships with it
4 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.
- today First seen · 215 lines · 127 tokens per session scan A 574ce5014b9e
git-workflow is a skill published in the GitHub repository ericrisco/rsc-harness (60 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 3,229 once invoked, about $0.0006 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
create-pr
Create GitHub pull requests with Conventional Commits-formatted titles and structured PR bodies. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
git-workflow
Covers the full git workflow for a software project: branch naming conventions, commit message authoring (Conventional Commits standard), PR description templates, and merge strategy advice. It produces ready-to-use git artefacts, not generic advice.
git-workflow-automation
Expert Git workflow automation for commit message generation, branch naming, PR description writing, changelog generation, merge conflict resolution, and release management. Activates when users say "write a commit message", "create a PR", "generate changelog", "branch name for", "resolve merge conflict", "cut a…
systematic-debugging
四阶段根因分析：调查、模式分析、假设测试、修复。铁律：没有根因就没有修复。禁止猜测性修复和症状压制。触发短语："调试"、"debug"、"排查"、"根因"。.
brainstorming
协作式需求探索与设计。用苏格拉底式对话将模糊想法转化为结构化的设计规格文档（spec.md）。触发短语："探索需求"、"讨论设计"、"头脑风暴"、"brainstorm"。.
daily
生成今日工作日报。仅在用户显式触发 /daily 时执行，不自动运行。.