Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Dqz00116/skill-libnpx agentmods add skills/dqz00116/skill-lib/git-workflowWrote 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/dqz00116/skill-lib/git-workflow)<a href="https://agentmods.dev/skills/dqz00116/skill-lib/git-workflow"><img src="https://agentmods.dev/badge/skills/dqz00116/skill-lib/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/dqz00116/skill-lib/git-workflow"><img src="https://agentmods.dev/badge/skills/dqz00116/skill-lib/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.01213 |
| Opus 5.5 | $0.00008 | $0.00485 |
| Sonnet 5.5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
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 1mo 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
Overview
Automate Git operations with safety checks and user confirmation. This skill ensures changes are reviewed and explicitly approved before committing or pushing.
When to Use
-
Checks Workspace Status
- Shows modified files
- Lists untracked files
- Detects conflicts or merge states
-
Smart Confirmation Prompt
- Lists all changes clearly
- Asks for explicit approval
- Provides multiple options (commit all, specific files, ignore, skip)
-
Safe Commit & Push
- Only commits after confirmation
- Handles GitHub authentication
- Reports success or failure
-
Conflict Detection
- Detects merge conflicts
- Suggests resolution steps
- Prevents force pushes
When NOT to use:
- When you need automated/unattended commits without user interaction
- When performing complex Git operations beyond standard commit/push workflows
- When a different skill or tool is explicitly designated for Git operations
Quick Start
Simple Commit
python scripts/git_commit.py
The script will:
- Show
git status - Ask for confirmation
- Commit and push if approved
Interactive Mode
python scripts/git_commit.py --interactive
Step-by-step confirmation for each file.
Confirmation Format
📋 **Git Status Summary:**
Modified:
- SOUL.md (41 insertions)
- README.md (5 deletions)
Untracked:
- new-feature.md
- temp.log (should be ignored?)
✅ **Confirm:**
Reply:
- "yes" → commit all modified
- "commit with untracked" → commit all including untracked
- "only SOUL.md" → commit specific file
- "ignore temp.log" → add to .gitignore
- "skip" → do nothing
Safety Rules
Never
- ❌ Commit without checking status first
- ❌ Commit without user confirmation
- ❌ Force push (
git push -f) - ❌ Commit binary/temporary files without asking
Always
- ✅ Check
git statusbefore any operation - ✅ Show list of changes for approval
- ✅ Respect
.gitignore - ✅ Handle errors gracefully
- ✅ Report what was done
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.
- 1mo ago First seen · 249 lines · 20 tokens per session scan A 58a90b168e7c
git-workflow is a skill published in the GitHub repository Dqz00116/skill-lib (22 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 1,213 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
git-commit
Create well-structured git commits using the Conventional Commits specification. Use when asked to "commit changes", "create a git commit", "stage and commit", "write a commit message", or "/commit". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
git-workflow
Consistent git practices, recovery patterns, and safe operations.
github-wiki-flat
GitHub Wiki has a flat namespace — no real folders, sidebar ordering tricks, link gotchas.
fix-once-auto-inject
One-time fixes get repeated manually.
github
Manage GitHub issues and pull requests, inspect CI runs, and query repository data.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.