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/irahardianto/rugged-gemini/git-workflownpx skills add irahardianto/rugged-gemini --skill git-workflowgit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/git-workflow)<a href="https://agentmods.dev/skills/irahardianto/rugged-gemini/git-workflow"><img src="https://agentmods.dev/badge/skills/irahardianto/rugged-gemini/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.1 | $0.00019 | $0.00956 |
| Opus 5 | $0.00010 | $0.00478 |
| Sonnet 5 | $0.00004 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
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 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Commits — Conventional Format
<type>(<scope>): <description>
[optional body]
[optional footer]
| Type | Purpose |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation |
| style | Formatting |
| refactor | No feature/fix change |
| test | Adding/updating tests |
| chore | Maintenance, deps |
| perf | Performance |
| ci | CI/CD config |
Rules: imperative mood ("add" not "added"), scope = feature area, <72 chars, body explains WHY.
Branch Naming
Format: <type>/<ticket-or-desc> (kebab-case)
feat/task-crud-api
fix/auth-token-expiry
refactor/storage-layer
chore/update-deps
Commit Hygiene
- One logical change per commit
- Never commit broken tests
- No debug code (console.log, TODO hacks)
- No secrets (use .gitignore + env vars)
PR Size
- Ideal: <400 lines. Acceptable: 400-800. Too large: >800 (split).
Merge Strategy
- Feature → main: squash merge
- Release: merge commit
- Hotfix: cherry-pick
Monorepo Strategies
When working in monorepos with multiple packages/services:
- Scope commits to package:
feat(api): add task endpoint— scope = package name - Changelogs per package: each package has its own CHANGELOG.md
- Selective CI: trigger builds only for affected packages (path filters)
- Shared deps: pin at workspace root, override per-package only when needed
- Atomic changes: cross-package changes in single commit when they must deploy together
Semantic Release Automation
For automated versioning and changelog generation:
- Conventional commits → version bumps:
feat→ minor,fix→ patch,BREAKING CHANGE→ major - Tooling:
semantic-release(Node.js),release-please(GitHub),go-semantic-release(Go) - CI integration: run after merge to main, generates tag + changelog + release
- Pre-release channels:
alpha,beta,rcfor pre-release testing
Worktree Best Practices
When orchestrator uses git worktrees for parallel agent execution:
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 · 113 lines · 19 tokens per session scan A c219dc77c6b9
git-workflow is a skill published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 956 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-08-31.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
crew-commit
Canonical commit workflow for Gas Town crew members: pre-flight checks, branch creation, gt commit with agent identity, push, and PR creation. Use when ready to commit and submit work for review.
cherry-pick
Cherry-pick a commit from main to a Sui release branch, create the release PR, and report the PR URL.
task-snapshot
Create a commit or tag snapshot only when explicitly requested for a milestone, reproducibility checkpoint, handoff, or pinned artifact.
mflux-pr
Make a clean PR in mflux (inspect diff, quick verification, commit, push, open PR) using repo conventions.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.