Borrowing it
Nothing to install: this file belongs to extra-org/extra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/extra-org/extra/main/.claude/skills/git-workflow/SKILL.mdgit clone --depth 1 https://github.com/extra-org/extraWrote 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/extra-org/extra/git-workflow)<a href="https://agentmods.dev/skills/extra-org/extra/git-workflow"><img src="https://agentmods.dev/badge/skills/extra-org/extra/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/extra-org/extra/git-workflow"><img src="https://agentmods.dev/badge/skills/extra-org/extra/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Memory Poisoning · line 3 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 19 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00038 | $0.00748 |
| Opus 5.5 | $0.00015 | $0.00299 |
| Sonnet 5.5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
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 2mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Git Workflow
Purpose
Work safely with Git: keep changes scoped and reviewable, never overwrite the user's work, and produce clear history.
When to Use This Skill
- Before editing files (inspect current state first).
- Branching, staging, or committing.
- Preparing a change set or pull request for review.
Files to Read First
AGENTS.md(git safety + scope rules).docs/DEVELOPMENT_WORKFLOW.md.- The current diff/status of the repository.
Core Principles
- Inspect before editing. Run
git statusandgit diffto understand uncommitted work; never clobber the user's changes. - Keep changes scoped to one task; avoid massive unrelated diffs.
- Don't reformat or move files outside scope.
- Commit only when asked. Do not auto-commit; never force-push shared branches or skip hooks.
- Clear messages. Use a conventional, scoped commit style.
- No secrets. Never stage
.env, credentials, or large binaries.
Process
- Inspect:
git statusandgit diff(andgit log --oneline -5for message style). Note any pre-existing uncommitted work to preserve. - Scope the change to the current task; keep unrelated edits out.
- Stage deliberately (
git add <paths>) — review what's staged; ensure no secrets or ignored files sneak in. - Commit when asked, using the format below and a HEREDOC for the message.
- Summarize the modified files in your final response.
Commit message format
Use a conventional prefix:
feat:a new feature/capabilityfix:a bug fixrefactor:behavior-preserving restructuringdocs:documentation onlytest:tests onlychore:tooling/config/housekeeping
Example: docs: consolidate agent instructions under .ai/
Checklist Before Finishing
- Inspected
git status/git diffbefore editing; no user work clobbered. - Change is scoped to one task; no unrelated churn.
- No secrets,
.env, or large binaries staged. - Commit message (if committing) uses the conventional format.
- Only committed because the user asked.
- Modified files summarized in the final response.
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.
- 2mo ago First seen · 89 lines · 38 tokens per session scan A 10ef9f9fc1ab
git-workflow is a skill published in the GitHub repository extra-org/extra (117 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 748 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
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
prepare-pr
Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.