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 Benja-Pauls/SerpentStack --skill git-workflowgit clone --depth 1 https://github.com/Benja-Pauls/SerpentStackWrote 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/benja-pauls/serpentstack/git-workflow)<a href="https://agentmods.dev/skills/benja-pauls/serpentstack/git-workflow"><img src="https://agentmods.dev/badge/skills/benja-pauls/serpentstack/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/benja-pauls/serpentstack/git-workflow"><img src="https://agentmods.dev/badge/skills/benja-pauls/serpentstack/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.00032 | $0.00272 |
| Opus 5.5 | $0.00013 | $0.00109 |
| Sonnet 5.5 | $0.00006 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
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
Branch Naming
Use prefixed branch names:
feature/short-description— new functionalityfix/short-description— bug fixeschore/short-description— tooling, dependencies, configrefactor/short-description— code restructuring
Lowercase, hyphens, under 50 characters.
Commit Messages
Follow Conventional Commits:
<type>: <short summary under 72 chars>
Types: feat, fix, chore, docs, test, refactor, style
Pull Request Format
gh pr create \
--title "feat: add projects endpoint" \
--body "## Summary
- What changed and why (1-3 bullets)
## Test plan
- How the changes were verified"
Pre-Push Checklist
Before pushing, run the full verification suite:
make verify # lint + typecheck + test for both backend and frontend
This runs the same checks as CI, so if it passes locally, CI will pass too.
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 · 50 lines · 32 tokens per session scan A dba94ecab087
git-workflow is a skill published in the GitHub repository Benja-Pauls/SerpentStack (2 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 272 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-31.
Other skills, from other repositories
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
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.
git-commit
Analyze changes with Git only and auto-generate conventional commit messages with optional emoji; suggests splitting commits when needed, runs local Git hooks by default (use --no-verify to skip).
git-master
MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog). Load it before running git yourself, or pass loadskills=['git-master'] to the task that commits. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims and hook env vars, pre-commit framework migration, Starlark git.sandbox checks and unstaged fixes, signed commits, managed workdirs, fork-PR trust gate (clone gate and posting gate), and auth via identities or…
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.