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/aigentive/ralphx/git-workflownpx skills add aigentive/RalphX --skill git-workflowgit clone --depth 1 https://github.com/aigentive/RalphXWhat 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.00009 | $0.00551 |
| Opus 5 | $0.00005 | $0.00275 |
| Sonnet 5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Commit Message Format
<type>: <description>
[optional body]
[optional footer]
Types
feat: New featurefix: Bug fixrefactor: Code change that neither fixes a bug nor adds a featuretest: Adding or updating testsdocs: Documentation only changeschore: Changes to build process or auxiliary toolsstyle: Formatting, missing semi-colons, etc.
Examples
feat: add user authentication
fix: resolve race condition in task loading
refactor: extract validation logic to separate module
test: add integration tests for API endpoints
docs: update README with setup instructions
chore: update dependencies
Atomic Commits
Principles
- One logical change per commit
- Tests should pass after each commit
- Can be reverted independently
- Easy to understand in isolation
Signs of Good Atomicity
- Commit message fits in one line
- All files relate to the same change
- No "and" needed to describe the change
- Tests still pass if commit is reverted
What to Avoid
- "Fix several bugs"
- Mixing refactoring with features
- Incomplete changes
- Unrelated file changes
Workflow
Before Committing
- Review changes:
git diff - Follow the target project's local instructions and run only the focused validation required for the change
- Run scoped linting when the target project requires it
- Stage specific files:
git add <files>
Commit Checklist
- Changes are tested
- Tests pass
- Lint passes
- Message follows convention
- No sensitive data included
Commands
# View changes
git status
git diff
git diff --staged
# Stage changes
git add <file> # Specific file
git add -p # Interactive staging (avoid -A)
# Commit
git commit -m "type: description"
# View history
git log --oneline -10
git log --stat -3
Safety Rules
Never
- Force push to main/master
- Commit secrets or credentials
- Commit without the target project's required focused validation
- Use
git add -Ablindly
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.
- yesterday First seen · 107 lines · 9 tokens per session scan A 1e8de5b78dd2
git-workflow is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 9 tokens to every session and 551 once invoked, about $0.0000 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…