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 dryvist/claude-code-plugins --skill git-workflow-standardsgit clone --depth 1 https://github.com/dryvist/claude-code-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/dryvist/claude-code-plugins/git-workflow-standards)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/git-workflow-standards"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/git-workflow-standards/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/dryvist/claude-code-plugins/git-workflow-standards"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/git-workflow-standards.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.00059 | $0.01154 |
| Opus 5.5 | $0.00024 | $0.00462 |
| Sonnet 5.5 | $0.00012 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
git-workflow-standards 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 25d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Standards
Worktree setup and structure: see superpowers:using-git-worktrees. This
skill covers what comes after the worktree exists.
Every branch with commits MUST have an associated PR. Orphaned branches must get a PR or be deleted.
Stale branch (worktree-paired, bare local, or remote-only — see
prune-branches, github-workflows, for the full procedure): a non-default
branch, checked out nowhere, unreferenced by any open PR (--head or
--base), with no uncommitted changes (when a worktree exists), and either
a merged PR whose headRefOid matches the branch tip, or zero commits ahead
of the default branch. Use git worktree remove (never --force) for
worktree-paired branches — Git blocks removal of dirty worktrees — and
git push origin --delete for a live remote ref, only after
prune-branches's pre-push ancestry re-check.
Branch Hygiene
- Sync the default branch daily:
git pull - Long-running branches: rebase from the default branch weekly
- Before PRs: ensure branch is on the latest default branch
- Never branch from feature branches — always from the default branch fresh
(git-flow repos:
git flow feature startbranches fromdevelop). The one exception is layering a PR stack, and only viagh stack; seepr-stacks(github-workflows). - Commit messages: conventional-commit prefixes only, no emoji (see
pr-standards)
Git Flow Repositories
For repositories using the Git Flow model (where the default branch is develop):
- Target Branch: All feature and bugfix branches must target and merge into
develop. - Validation: Once changes are merged into
develop, they must be thoroughly validated against production/tested ondevelop. - End-of-Session Promotion: At the end of every session, all changes on
developMUST be merged intomainvia/promote-release. This promotion is a mandatory, non-optional step. - Planning Checklist: You must explicitly add "Merge develop into main (promote release)" to your session to-do / plan checklist at the start of work.
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.
- 25d ago Changed · -3 lines 4ca5c7bfbb7c
- 1mo ago Changed · +3 lines ebd63716cb1c
- 1mo ago First seen · 100 lines · 59 tokens per session scan A f767dc962fb5
git-workflow-standards is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,154 once invoked, about $0.0002 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
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…