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 sequenzia/claude-plugins --skill git-workflowgit clone --depth 1 https://github.com/sequenzia/claude-pluginsWrote 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/sequenzia/claude-plugins/git-workflow)<a href="https://agentmods.dev/skills/sequenzia/claude-plugins/git-workflow"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/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/sequenzia/claude-plugins/git-workflow"><img src="https://agentmods.dev/badge/skills/sequenzia/claude-plugins/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.00012 | $0.00491 |
| Opus 5.5 | $0.00005 | $0.00196 |
| Sonnet 5.5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $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 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.
What it actually says
Git Workflow
This skill routes git operations to the appropriate commands based on user intent.
When to Use
Trigger this skill when the user wants to:
- Commit only: "commit changes", "save changes", "commit this", "commit it", "commit my work"
- Push only: "push changes", "push to remote", "push it up", "push this", "push it"
- Both: "commit and push", "ship it", "send it up", "save and push"
Behavior
Commit Only
When the user's intent is to commit without pushing:
Trigger phrases: commit, save changes, commit this, commit it, commit my work
Action: Run /dev-tools:git-commit
Push Only
When the user's intent is to push existing commits without creating a new commit:
Trigger phrases: push, push changes, push to remote, push it up, push it
Action: Run /dev-tools:git-push
Commit and Push
When the user wants to commit their changes AND push them to the remote:
Trigger phrases: commit and push, ship it, send it up, save and push
Action: Run /dev-tools:git-commit first, then /dev-tools:git-push
Decision Logic
- Parse the user's request for intent keywords
- If request contains "push" but NOT "commit" → push only
- If request contains "commit" or "save" but NOT "push" → commit only
- If request contains both "commit" and "push" → commit then push
- If request matches "ship it" or "send it up" → commit then push
Notes
- The commit command stages all changes before committing
- The push command handles upstream conflicts with automatic rebase
- If commit fails (e.g., pre-commit hook), do not proceed to push
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 · 68 lines · 12 tokens per session scan A 239437918821
git-workflow is a skill published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 491 once invoked, about $0.0000 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.