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 aretw0/agents-lab --skill git-workflowgit clone --depth 1 https://github.com/aretw0/agents-labWrote 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/aretw0/agents-lab/git-workflow)<a href="https://agentmods.dev/skills/aretw0/agents-lab/git-workflow"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/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/aretw0/agents-lab/git-workflow"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/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.00040 | $0.00646 |
| Opus 5.5 | $0.00016 | $0.00258 |
| Sonnet 5.5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00065 |
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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Help with Git operations and workflow strategy.
Branch Strategy
# Inspect current state
git branch -a
git log --oneline -20
git status
Recommend strategy based on project context:
- Solo:
main+ short-lived feature branches - Team:
main+develop+feature/*/fix/*branches - Release cadence: GitFlow (
main/develop/release/*/hotfix/*)
PR / MR Workflow
git diff main --stat— review what changed- Draft a clear title and description
- Suggest reviewers based on touched files:
git log --format='%an' -- <files> - Always include the full PR/MR URL in any summary or status update:
Retrieve with:PR: https://github.com/owner/repo/pull/42gh pr view --json url --jq .url(GitHub) orglab mr view --output json | jq .web_url(GitLab)
Conflict Resolution
git diff --name-only --diff-filter=U— find conflicted files- Read each conflicted file
- Understand both sides of the conflict
- Resolve with minimal changes, preserving intent from both sides
Interactive Rebase
Guide through git rebase -i for cleaning history before a PR.
If resolving conflicts during rebase, continue non-interactively:
GIT_EDITOR=true git rebase --continue
Non-Interactive Safety
When the agent runs git or gh/glab, never open an interactive editor or prompt.
Commits — always pass message on the command line:
git commit -m "fix(scope): message"
Rebase continue — --no-edit is not supported, use:
GIT_EDITOR=true git rebase --continue
# or
git -c core.editor=true rebase --continue
Merge — reuse existing message:
git merge --no-edit
Any other git command that could open an editor:
GIT_EDITOR=true git <command>
GitHub CLI — disable prompts and provide all fields explicitly:
GH_PROMPT_DISABLED=1 gh pr create --title "..." --body "..."
GH_PROMPT_DISABLED=1 gh pr merge --squash --delete-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 · 94 lines · 40 tokens per session scan A 5128e35f6ddd
git-workflow is a skill published in the GitHub repository aretw0/agents-lab (11 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 646 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-30.
Other skills, from other repositories
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
release
Create a new versioned release with changelog. Bumps version in code, updates CHANGELOG.md, commits, tags, and pushes using the repository release flow. GitHub Actions creates the release and uses only the current changelog section as release notes. Use when the user says "release", "cut a release", "bump version"…
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
pi-release-workflow
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.