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 The-AI-Directory-Company/agents-and-skills --skill git-workflow-guidegit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/git-workflow-guide)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/git-workflow-guide"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/git-workflow-guide/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/the-ai-directory-company/agents-and-skills/git-workflow-guide"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/git-workflow-guide.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.00031 | $0.01226 |
| Opus 5 | $0.00015 | $0.00613 |
| Sonnet 5 | $0.00006 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
git-workflow-guide 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Guide
Before you start
Confirm the following for the project:
- What is the branching model? — Trunk-based, GitFlow, or GitHub Flow
- What is the main branch name? —
mainormaster - Are there branch protection rules? — Required reviews, CI checks, linear history
- What is the merge strategy? — Squash, rebase, or merge commit
- Is there a commit message convention? — Conventional Commits, Angular, or custom
If these are not documented, ask the team lead before establishing your own pattern. Inconsistency in git workflows creates merge conflicts and confusion.
Branch naming
Use this format:
<type>/<ticket-id>-<short-description>
Types:
feat/— New featurefix/— Bug fixrefactor/— Code restructuring without behavior changedocs/— Documentation onlytest/— Adding or updating testschore/— Build, CI, dependency updates
Examples:
feat/PROJ-123-add-user-search
fix/PROJ-456-null-check-login
refactor/PROJ-789-extract-auth-module
chore/update-eslint-config
Rules:
- Lowercase only
- Hyphens between words, not underscores
- Include ticket ID when one exists
- Keep the description under 5 words
- Delete branches after merging
Commit messages
Format
<type>(<scope>): <subject>
<body>
<footer>
Type (required)
feat, fix, refactor, docs, test, chore, perf, ci, style
Scope (optional)
The module, component, or area affected: auth, api, ui, db, ci
Subject (required)
- Imperative mood: "add" not "added" or "adds"
- Lowercase first letter
- No period at the end
- Max 72 characters
Examples
feat(auth): add password reset flow ← feature with scope
fix(api): handle null user ID in session ← bug fix with scope
chore: update TypeScript to 5.4 ← chore, no scope needed
refactor(db): extract query builder module ← refactor with scope
Add a body for non-trivial changes explaining WHY, not HOW. Reference tickets in the footer: Closes #234.
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 · 156 lines · 31 tokens per session scan A e1beec2eb38b
git-workflow-guide is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,226 once invoked, about $0.0002 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
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
git-commit
Conventional Commits format for git commits and PR/MR titles. Type prefixes, scope rules, breaking change syntax, and commit message structure. Use when committing changes, writing commit messages, creating PR/MR titles, or formatting squash merge messages. Not for PR workflows (git-pr), CI/CD status (git-ci), or git…
commit-message-expert
Generates consistent, meaningful Git commit messages based on a diff or description of changes. Use when writing or reviewing a commit message, especially to follow Conventional Commits or a project's existing convention.
secrets-scanner
Narrowly scans code and config for hardcoded secrets, credentials, API keys, and tokens. Use before a commit/PR, or when auditing a codebase for accidentally-committed secrets.
git-hook-automation-designer
Configures pre-commit and pre-push hooks (Husky, Lefthook) for fast lint-staged, branch naming, and secret blocking.