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 khalilbenaz/claude-skills-collection --skill git-workflow-helpergit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/git-workflow-helper)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/git-workflow-helper"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/git-workflow-helper/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/khalilbenaz/claude-skills-collection/git-workflow-helper"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/git-workflow-helper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 60 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 148 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 85 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 147 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00096 | $0.01620 |
| Opus 5 | $0.00048 | $0.00810 |
| Sonnet 5 | $0.00019 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
git-workflow-helper 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 7d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Helper
1. Diagnostic initial
Avant toute action, évaluer la situation :
git status # état de l'index et du working tree
git log --oneline --graph -15 # historique visuel récent
git stash list # stashs en attente
git remote -v # remotes configurées
Identifier : branche courante, commits non-pushés, fichiers modifiés/stagés, conflits actifs.
2. Résolution de conflits de merge
Étapes :
- Lancer le merge ou rebase, observer les conflits :
git merge feature/ma-branche # ou git rebase main - Lister les fichiers en conflit :
git diff --name-only --diff-filter=U - Éditer chaque fichier : supprimer les marqueurs
<<<<<<<,=======,>>>>>>>, garder le bon code. - Marquer comme résolu et continuer :
git add <fichier-résolu> git merge --continue # ou git rebase --continue - En cas d'impasse, annuler proprement :
git merge --abort # ou git rebase --abort
Outil visuel (recommandé) :
git mergetool # ouvre vimdiff, VS Code, IntelliJ selon config
3. Annuler / corriger des commits
| Situation | Commande | Risque |
|---|---|---|
| Défaire le dernier commit (garder les modifs) | git reset --soft HEAD~1 |
Faible |
| Défaire le dernier commit (perdre les modifs) | git reset --hard HEAD~1 |
Destructif |
| Corriger le message du dernier commit | git commit --amend --no-edit |
Faible si pas pushé |
| Annuler un commit déjà pushé (safe) | git revert <sha> |
Nul — crée un commit inverse |
| Supprimer un commit du milieu de l'historique | git rebase -i HEAD~N |
Modéré |
Règle d'or : ne jamais --force-push sur main/master. Sur une branche feature partagée, prévenir l'équipe.
4. Rebase interactif — recette type
git fetch origin
git rebase -i origin/main
Dans l'éditeur, remplacer pick par :
squash(s) — fusionner dans le commit précédentreword(r) — changer le messagedrop(d) — supprimer le commitfixup(f) — squash sans garder le message
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.
- 7d ago First seen · 196 lines · 96 tokens per session scan A f141194775a6
git-workflow-helper is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 16d ago), licensed MIT. It adds 96 tokens to every session and 1,620 once invoked, about $0.0005 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
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
commit
Creates Conventional Commits with pre-commit validation. Triggers: commit, conventional commit, git commit, message.
night-watch
Autonomous maintenance (dep updates, dead code, small refactors) in isolated branch, off-hours. Triggers: night watch, autonomous maintenance, dep updates.
git-conventions
Conventional Commits only (feat, fix, docs, refactor, test, chore); no AI co-authorship trailer and no AI signature in a commit message. Triggers: commit, git, message, changelog, release, pull request.
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.