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 ancoleman/ai-design-components --skill managing-git-workflowsgit clone --depth 1 https://github.com/ancoleman/ai-design-componentsWrote 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/ancoleman/ai-design-components/managing-git-workflows)<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/managing-git-workflows"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/managing-git-workflows/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/ancoleman/ai-design-components/managing-git-workflows"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/managing-git-workflows.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.00060 | $0.02354 |
| Opus 5.5 | $0.00024 | $0.00942 |
| Sonnet 5.5 | $0.00012 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
managing-git-workflows 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflows
Implement structured Git workflows for team collaboration, code quality, and automated releases. This skill covers branching strategies, conventional commit formats, Git hooks, and monorepo management patterns.
When to Use This Skill
Use this skill when:
- Choosing a branching strategy for a new project or team
- Implementing consistent commit message formats
- Setting up Git hooks for linting, testing, or validation
- Managing monorepos with multiple projects
- Establishing code review workflows
- Automating versioning and releases
Quick Decision: Which Branching Strategy?
Trunk-Based Development
Use when the team has strong CI/CD automation, comprehensive test coverage (80%+), and deploys frequently (daily or more). Short-lived branches merge within 1 day. Requires feature flags for incomplete features.
Best for: High-velocity teams with mature DevOps practices (Google, Facebook, Netflix)
GitHub Flow
Use for web applications with continuous deployment. Main branch always represents production. Simple PR-based workflow for small to medium teams (2-20 developers).
Best for: Startups, SaaS products, open-source projects
GitFlow
Use when supporting multiple production versions simultaneously, requiring formal QA cycles, or following scheduled releases (monthly, quarterly). More complex but structured.
Best for: Enterprise software, mobile apps with App Store releases, on-premise products
For detailed branching patterns with examples, see references/branching-strategies.md.
Conventional Commits
Structure commit messages for automated versioning and changelog generation:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Common Types:
feat- New feature (MINOR version bump: 0.1.0)fix- Bug fix (PATCH version bump: 0.0.1)docs- Documentation onlyrefactor- Code restructuring without feature changetest- Adding or updating testschore- Maintenance tasks
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/gitflow-example.sh 6.9 KB runs code
- examples/github-flow-example.sh 4.0 KB runs code
- outputs.yaml 7.7 KB
- references/branching-strategies.md 14 KB
- references/code-review-workflows.md 14 KB
- references/conventional-commits.md 15 KB
- references/git-hooks-guide.md 14 KB
- references/monorepo-patterns.md 17 KB
- scripts/check-branch-name.sh 5.3 KB runs code
- scripts/setup-hooks.sh 6.8 KB runs code
- scripts/validate-commit-msg.sh 4.7 KB runs code
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 · 344 lines · 60 tokens per session scan A 888a8588a4cd
managing-git-workflows is a skill published in the GitHub repository ancoleman/ai-design-components (525 stars, last pushed 10mo ago), licensed MIT. It adds 60 tokens to every session and 2,354 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-30.
Other skills, from other repositories
github-standards
GitHub repository standards and workflow rules. Use when creating repos, opening PRs, pushing code, setting up CI, creating branches, writing READMEs, or reviewing repo hygiene. Covers commit format (complements git-commit skill), PR message template, sensitive data pre-commit checks, repo naming, README requirements…
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.