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 agentmods add skills/jonlwowski012/copilot-agent-factory/git-workflownpx skills add jonlwowski012/copilot-agent-factory --skill git-workflowgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/jonlwowski012/copilot-agent-factory/git-workflow)<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/git-workflow"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/git-workflow.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.02598 |
| Opus 5 | $0.00009 | $0.01299 |
| Sonnet 5 | $0.00003 | $0.00520 |
| Haiku 4.5 | $0.00002 | $0.00260 |
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 4d 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 — 521 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Git Workflow
When to Use This Skill
This skill activates when you need to:
- Understand the project's Git workflow
- Create branches following project conventions
- Write commit messages properly
- Submit pull requests correctly
- Manage Git history
Prerequisites
- Git installed
- Repository cloned
- Understand basic Git commands
Step-by-Step Workflow
Step 1: Check Project Git Conventions
Look for documentation:
CONTRIBUTING.md- Contribution guidelines.github/PULL_REQUEST_TEMPLATE.md- PR template.github/ISSUE_TEMPLATE/- Issue templatesREADME.md- Git workflow section
Common patterns to detect:
- Branch naming:
feature/,bugfix/,hotfix/ - Commit conventions: Conventional Commits, Angular style
- PR requirements: Tests, documentation, reviews
Step 2: Create a New Branch
Check current branch:
git branch
git status
Update main/master branch:
# Switch to main branch
git checkout main # or master
# Pull latest changes
git pull origin main
Create new branch:
Common naming conventions:
# Feature branch
git checkout -b feature/add-user-authentication
git checkout -b feature/issue-123-add-login
# Bug fix
git checkout -b bugfix/fix-login-redirect
git checkout -b fix/issue-456-memory-leak
# Hotfix (urgent production fix)
git checkout -b hotfix/security-patch-v1.2.1
# Refactor
git checkout -b refactor/improve-database-queries
# Documentation
git checkout -b docs/update-api-documentation
# Release branch
git checkout -b release/v1.2.0
Branch naming best practices:
- Lowercase with hyphens
- Include issue/ticket number if available
- Descriptive but concise
- Follow project pattern
Step 3: Make Changes and Commit
Check changes:
git status
git diff
Stage changes:
# Stage specific files
git add file1.py file2.js
# Stage all changes
git add .
# Stage interactively
git add -p
Write commit messages:
Conventional Commits format:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
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.
- 4d ago First seen · 521 lines · 17 tokens per session scan A c8717d5e0ded
git-workflow is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 2,598 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
git-commit
Generate well-formatted git commit messages following conventional commit standards.
test-repo
Use this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and checkpoint creation work correctly.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
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…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…