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/kreek/consult/git-workflownpx skills add kreek/consult --skill git-workflowgit clone --depth 1 https://github.com/kreek/consultWhat 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.00024 | $0.01432 |
| Opus 5 | $0.00012 | $0.00716 |
| Sonnet 5 | $0.00005 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
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 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 — 120 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.
Git history is a review, bisect, revert, and release surface. Keep it recoverable, scoped, and honest. 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, or force-push decisions.
When NOT to Use
- Staging reviewed files, splitting commit groups, writing commit messages, or
committing approved work. Use
commit. - Reviewing implementation correctness; use
code-review. - Refactor planning; use
refactoring. - CI failure triage; use
debuggingto reproduce and root-cause the failing check.
Core Ideas
- Inspect before mutation. Know the tree, branch, and upstream state before any history operation.
- Prefer
--force-with-lease --force-if-includesover bare force when a solo-branch rewrite is genuinely needed. - Preserve a recovery point (tag, named branch, or noted reflog entry) before any risky operation.
- Resolve conflicts by preserving intent from both sides, then run the relevant checks.
- Test hook policy, not hook wrappers. Tiny hooks that only
execa repo script don't need dedicated tests; test the script when it selects commands, blocks branches, routes staged files, or handles failures. - 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; do not add a second chat-level ask on top of an approval the host has granted. Reserve your own questions for GitHub writes that publish user-owned text (PRs, issues, comments) and for destructive operations. Check which surface exists before planning the step (ghCLI, GitHub MCP, or built-in host tools);ghis absent from some sandboxes and hosted sessions. - Humans approve PR and issue text before it is published. Titles and descriptions are author-facing content the user owns. Draft the title and body locally, show them, and get explicit approval of that exact text before anything creates or updates the PR or issue. Do not let a tool open an editor or send unreviewed body text.
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.
- 2d 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 7d ago), licensed MIT. It adds 24 tokens to every session and 1,432 once invoked, about $0.0001 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-31.
Other skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
scaffold
Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
organize
Repository structure only: directory layout, file placement, naming conventions, and where-does-this-belong decisions. Detects the project's convention, audits files against it, and executes move plans with import-path updates. Never changes code inside files beyond the import updates a move forces; in-file…