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 subhansh-dev/agent-maxxing --skill git-workflowgit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/subhansh-dev/agent-maxxing/git-workflow)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/git-workflow"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/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/subhansh-dev/agent-maxxing/git-workflow"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/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.00020 | $0.00493 |
| Opus 5 | $0.00010 | $0.00246 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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.
What it actually says
Git Workflow — How to Use Git Properly
Commit Messages
Format: <type>(<scope>): <description>
Types:
feat— new featurefix— bug fixrefactor— code restructuring without behavior changestyle— formatting, no code changedocs— documentation onlytest— adding or updating testschore— maintenance tasksperf— performance improvement
Examples:
feat(auth): add OAuth2 login flowfix(api): handle null response from payment gatewayrefactor(parser): extract validation into separate moduleperf(db): add index for user lookup query
Rules:
- Subject line: imperative mood, no period, max 72 chars
- Body: explain WHAT and WHY, not HOW (the code shows HOW)
- Reference issues:
Closes #123,Fixes #456
Branching
main— always deployablefeat/<name>— new featuresfix/<name>— bug fixesrefactor/<name>— refactoringchore/<name>— maintenance
Create branch from main, merge back via PR.
PR Workflow
- Create branch from main
- Make changes, commit incrementally
- Push branch
- Create PR with description
- Request review
- Address feedback
- Merge (squash for clean history)
Conflict Resolution
git fetch origingit rebase origin/main- Fix conflicts in files
git add <resolved-files>git rebase --continuegit push --force-with-lease
Never merge main into your branch — rebase instead.
Interactive Rebase
Clean up commits before PR:
git rebase -i HEAD~5
# squash, reword, edit commits
git push --force-with-lease
Stashing
git stash push -m "WIP: login form"
git stash list
git stash pop
Stash before switching branches. Pop when you return.
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 · 82 lines · 20 tokens per session scan A 83b72459323b
git-workflow is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 493 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
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
ship-it
A GitHub delivery workflow that commits completed changes, pushes a branch, creates and merges a pull request, and closes the related issue.
commit
A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.
writing-git-commits
Write clear, focused Git commit messages and keep commits easy to review.
speq-git-discipline
Read-only git guardrails and the Conventional Commits reference — no history writes, verify changes before completing. Triggered by planner-agent, implementer-agent, implementer-expert-agent, and recorder-agent. The headless orchestrators speq-plan-pr and speq-implement-pr are the sole exception: they write git…
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.