Borrowing it
Nothing to install: this file belongs to frostney/pascal-mcp-sdk. 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/frostney/pascal-mcp-sdk/main/.agents/skills/git-workflow/SKILL.mdgit clone --depth 1 https://github.com/frostney/pascal-mcp-sdkWrote 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/frostney/pascal-mcp-sdk/git-workflow)<a href="https://agentmods.dev/skills/frostney/pascal-mcp-sdk/git-workflow"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/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/frostney/pascal-mcp-sdk/git-workflow"><img src="https://agentmods.dev/badge/skills/frostney/pascal-mcp-sdk/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.00054 | $0.00388 |
| Opus 5.5 | $0.00022 | $0.00155 |
| Sonnet 5.5 | $0.00011 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
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 1mo 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.
What it actually says
Git workflow
Apply these defaults unless the user explicitly overrides them in the same turn. A git request authorizes only the repository and forge state required for that operation.
- Resolve the base from the remote default; never hardcode
main. - Before the first edit in any newly selected, created, or reused branch or worktree, require a clean worktree and fetch the remote default branch. Stop and report dirty files; never stash, commit, or discard them automatically.
- Create focused branches and worktrees directly from the freshly fetched remote default tip. Do not configure a focused branch to track the remote default; set its upstream only when pushing that focused branch.
- When entering an existing focused branch or worktree, merge the freshly fetched remote default before editing.
- Merge the remote base to update a branch. Never rebase.
- Stop and report merge conflicts; do not bypass or rewrite them.
- Never amend commits. Add a new commit for every correction.
- Never force-push. Stop if a plain push is rejected by divergent history.
- Stage only relevant files and exclude secrets or unrelated local work.
- Use concise Conventional Commit subjects in imperative mood.
- Let hooks run unless the user explicitly asks otherwise.
- Squash-merge pull requests and delete the source branch afterward.
After a squash merge, sync the local base and remove the merged local branch.
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.
- 1mo ago First seen · 38 lines · 54 tokens per session scan A 9fdd95be154a
git-workflow is a skill published in the GitHub repository frostney/pascal-mcp-sdk (2 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 388 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-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
studio-source-control
Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.
commit-and-push
Stage, commit, and push changes without opening a PR. Use when the user says "commit and push", "commit these to a new branch", "push this branch", or wants a branch + commit summary but does not want PR creation. Distinct from yeet, which owns the commit + push + PR flow.
pr
Create a pull request using the Dedalus PR template. Injects git state, commit history, and diff stats automatically.
git-workflow
Trunk-based git workflow with worktrees, switch/restore over checkout, Conventional Commits, force-with-lease. Use whenever the user asks me to commit, push, branch, or rebase.