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/d4rkninja/arcforge/git-workflowsnpx skills add d4rkNinja/arcforge --skill git-workflowsgit clone --depth 1 https://github.com/d4rkNinja/arcforgeWhat 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.00102 | $0.03240 |
| Opus 5 | $0.00051 | $0.01620 |
| Sonnet 5 | $0.00020 | $0.00648 |
| Haiku 4.5 | $0.00010 | $0.00324 |
Grade A, and why
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 2d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think Through Git & Repository Workflows
Production guidance for Git as a content-addressed graph, a distributed state machine, and one layer of a larger repository policy and release system. This skill is not a command cheat sheet and does not assume classical Gitflow is the right workflow.
Core principle: Observe the exact state, establish the expected old state, make the smallest authorized transition, and verify the authoritative result. A branch or tag is a mutable ref; a commit OID identifies an immutable object; hosted approvals, CI, protections, releases, and deployments are separate state.
Domain Law
NO GIT MUTATION WITHOUT:
1. the repository, worktree/index/sequencer state, and unrelated user changes inspected;
2. the exact object/ref transition and publication state identified;
3. local versus remote/hosted authority made explicit;
4. concurrency, retry, recovery, CI, release, and consumer effects handled;
5. the resulting graph, refs, worktree, policy state, and evidence verified.
When to Use
Use this skill when:
- choosing Gitflow, trunk-based development, short-lived branches, release branches, or a pull-request workflow;
- creating, changing, merging, rebasing, cherry-picking, deleting, or recovering branches and commits;
- resolving conflicts or an interrupted merge, rebase, or cherry-pick;
- fetching, pulling, pushing, force-updating, or coordinating refs across clones;
- creating or publishing Git tags and software versions;
- changing protected branches/tags, required checks, reviews, merge queues, signing, or repository policy;
- designing Git-aware CI, release provenance, backports, monorepo/multi-repo workflows, LFS, or submodules;
- removing secrets or sensitive data from history, rewriting shared history, or migrating a default branch/workflow;
- diagnosing corruption, lost commits, reflog recovery, repository scale, shallow/partial/sparse clones, or cross-platform checkout behavior.
When Not to Use
- For deployment pipeline implementation and artifact promotion, also use
runtime-delivery. - For the final production-readiness verdict and current test evidence, also use
quality-release. - For secret rotation, credential lifecycle, cryptographic policy, or untrusted CI boundaries, also use
security-privacy. - For a whole-system or organization-wide source-platform architecture decision, use
system-architecture-harness; usearchitecture-review-gatefor independent approval.
What ships with it
3 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.
- 2d ago First seen · 165 lines · 102 tokens per session scan A a498d2be1f52
git-workflows is a skill published in the GitHub repository d4rkNinja/arcforge (16 stars, last pushed 6d ago), licensed MIT. It adds 102 tokens to every session and 3,240 once invoked, about $0.0005 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-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
release
Create a new es-toolkit release (version bump, changelog, tag).
git-workflow
安全处理 Git 状态检查、提交信息、commit、分支、push、PR 和 rebase。用于用户要求检查改动、生成或创建提交、管理分支、推送、发起 PR 或整理历史时；严格区分每个动作的授权，并保护工作树中已有和无关的修改。.