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 kreek/consult --skill git-workflowgit clone --depth 1 https://github.com/kreek/consultWrote 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/kreek/consult/git-workflow)<a href="https://agentmods.dev/skills/kreek/consult/git-workflow"><img src="https://agentmods.dev/badge/skills/kreek/consult/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/kreek/consult/git-workflow"><img src="https://agentmods.dev/badge/skills/kreek/consult/git-workflow.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.00907 |
| Opus 5.5 | $0.00010 | $0.00363 |
| Sonnet 5.5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00091 |
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 16d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Iron Law
NEVER REWRITE SHARED HISTORY OR SKIP RECOVERY.
The host owns git mechanics and access permission. This skill owns the gates: recoverability and approval of published text.
When to Use
- Rebases, merge conflicts, bisects, reflog recovery, branch cleanup, PR history repair, force-push decisions, or any GitHub access.
When NOT to Use
- Staging, splitting, or committing reviewed work; use
commit. - Issue hierarchy, sizing, and tracker fields; use
issue-tracking. - Reviewing correctness; use
code-review. Refactor planning; userefactoring. CI failure triage; usedebugging.
Rules
- Branch without ceremony. Starting new work on the default branch, create
a topic branch first. On an existing topic branch, keep going unless the
new work is clearly unrelated; then branch off
mainand say which branch received the work. Do not ask which branch to use. - The host's permission system owns GitHub access. Hosts already gate network
calls and
ghunder the user's account, so do not add a second chat-level ask on top of an approval the host granted. Reserve your own questions for writes that publish user-owned text and for destructive operations. Identify the surface first (ghCLI, GitHub MCP, or host tools);ghis absent from some sandboxes, which does not mean GitHub is out of reach. - Humans approve PR and issue text before it is published. Draft the title and body locally, show them, and get approval of that exact text. Never let a tool open an editor or send unreviewed text.
- Inspect tree, branch, and upstream state before any history operation, and
stop on unexpected state. Name a recovery point (tag, branch, or reflog
entry) and whether the branch is local, solo, or shared before rewriting,
deleting, or force-pushing. Shared history is rewritten only with explicit
approval; force pushes use
--force-with-lease --force-if-includes. - Resolve conflicts by preserving intent from both sides, then run the
relevant checks. Verify with
range-diffor log inspection that intended commits remain. - Test hook policy, not hook wrappers. A hook that only execs a repo script needs no test; the script that selects commands, blocks branches, or routes files does.
- This skill never bypasses the host's sandbox or approval gates.
What ships with it
1 file 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.
- 16d ago Changed · +2 lines f5cc71482386
- 1mo ago Changed · -49 lines fb2948bf748d
- 1mo ago First seen · 120 lines · 24 tokens per session scan A 780121c847d7
git-workflow is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 17d ago), licensed MIT. It adds 24 tokens to every session and 907 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-31.
Other skills, from other repositories
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.
coordinate-worktrees-and-threads
Assign worktree, branch, write, validation, integration, and cleanup ownership before parallel repository work. Use when a worker will inspect or modify repository state outside the coordinator's worktree.
gh-stack
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
pr-create
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on…