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 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/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/jonlwowski012/copilot-agent-factory/git-workflow"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 194 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 430 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 444 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 506 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00017 | $0.02598 |
| Opus 5.5 | $0.00007 | $0.01039 |
| Sonnet 5.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 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 — 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.
- 1mo 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 1mo ago), licensed MIT. It adds 17 tokens to every session and 2,598 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.