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/higoralves/orc/git-advanced-workflowsnpx skills add HigorAlves/orc --skill git-advanced-workflowsgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/git-advanced-workflows)<a href="https://agentmods.dev/skills/higoralves/orc/git-advanced-workflows"><img src="https://agentmods.dev/badge/skills/higoralves/orc/git-advanced-workflows.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.00047 | $0.00607 |
| Opus 5 | $0.00023 | $0.00303 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
git-advanced-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 today.
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Advanced Workflows
Master advanced Git techniques to maintain clean history, collaborate effectively, and recover from any situation with confidence.
When to Use This Skill
- Cleaning up commit history before merging
- Applying specific commits across branches
- Finding commits that introduced bugs
- Working on multiple features simultaneously
- Recovering from Git mistakes or lost commits
- Managing complex branch workflows
- Preparing clean PRs for review
- Synchronizing diverged branches
Which Tool for Which Situation
| Situation | Tool | Reference |
|---|---|---|
| Clean up / squash / reword / reorder / split commits before a PR | Interactive rebase | references/rebase.md |
Update a feature branch with main, decide rebase vs merge |
Rebase / merge | references/rebase.md |
| Apply a single commit (e.g. hotfix) to other branches/releases | Cherry-pick | references/cherry-pick.md |
| Apply only specific files from a commit | Partial cherry-pick | references/cherry-pick.md |
| Find the commit that introduced a bug | Bisect | references/bisect.md |
| Work on multiple branches at once without stashing | Worktrees | references/worktrees.md |
| Recover lost commits / deleted branches / undo a bad reset | Reflog & recovery | references/reflog-recovery.md |
| Abort an in-progress rebase/merge/cherry-pick/bisect | Recovery commands | references/reflog-recovery.md |
| Safety rules before rewriting shared history | Best practices & pitfalls | references/history-rewrite.md |
Read the matching references/*.md file when you need the detailed commands and worked examples for that situation. Load only the references relevant to the task at hand.
References
references/rebase.md- interactive rebase operations, clean-up-before-PR workflow, rebase vs merge strategy, autosquash, splitting commits.references/cherry-pick.md- cherry-picking single commits/ranges, hotfix-to-multiple-releases workflow, partial (per-file) cherry-pick.references/bisect.md- manual and automatedgit bisectto locate a bug-introducing commit.references/worktrees.md- managing multiple worktrees for simultaneous multi-branch development.references/reflog-recovery.md- using reflog to recover lost commits/branches, undo resets, and abort in-progress operations.references/history-rewrite.md- cross-cutting best practices and common pitfalls when rewriting history (force-with-lease, backups, public branches).
What ships with it
6 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.
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.
- today First seen · 45 lines · 47 tokens per session scan A babfe75bfcde
git-advanced-workflows is a skill published in the GitHub repository HigorAlves/orc (6 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 607 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
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步（architecture-sync）。OpenCode / Claude / Codex / Cursor 通用。.
taiyi-diagram-c4
TaiyiForge 辅助 — 从代码反推 C4 架构文档（Observed/Inferred 分层 · Mermaid 真源）。OpenCode / Claude / Codex / Cursor 通用。.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.