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 bybren-llc/a-safe-pulse --skill git-advancedgit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/bybren-llc/a-safe-pulse/git-advanced)<a href="https://agentmods.dev/skills/bybren-llc/a-safe-pulse/git-advanced"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/git-advanced/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/bybren-llc/a-safe-pulse/git-advanced"><img src="https://agentmods.dev/badge/skills/bybren-llc/a-safe-pulse/git-advanced.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.00062 | $0.01584 |
| Opus 5 | $0.00031 | $0.00792 |
| Sonnet 5 | $0.00012 | $0.00317 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
git-advanced 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 3d 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.
This is a copy
100% identical to git-advanced — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Advanced Skill
TEMPLATE: This skill uses
{{PLACEHOLDER}}tokens. Replace with your project values before use.
Purpose
Provide guidance for advanced git operations with safety considerations. This project uses a rebase-first workflow with linear history -- understand these patterns to avoid breaking the codebase.
When This Skill Applies
- Rebasing feature branches onto dev
- Using git bisect to find bugs
- Cherry-picking commits between branches
- Resolving complex merge conflicts
- Recovering from git mistakes
Stop-the-Line Conditions
FORBIDDEN Operations
# FORBIDDEN: Force push to protected branches
git push --force origin dev # NEVER
git push --force origin master # NEVER
# FORBIDDEN: Merge commits on dev branch
git merge feature-branch # Use rebase-and-merge PR strategy
# FORBIDDEN: Skip pre-commit hooks
git commit --no-verify # Hooks exist for a reason
# FORBIDDEN: Rewriting shared history
git rebase -i HEAD~5 && git push --force # If already pushed
SAFE Operations
# SAFE: Force-with-lease on your feature branch
git push --force-with-lease origin ASP-XXX-feature
# SAFE: Interactive rebase before first push
git rebase -i origin/dev
# SAFE: Force push after conflict resolution on your own branch
git rebase origin/dev && git push --force-with-lease origin ASP-XXX-feature
Rebase Workflow (Standard)
Before Creating PR
# 1. Fetch latest changes
git fetch origin dev
# 2. Rebase onto latest
git rebase origin/dev
# 3. If conflicts, resolve them
git status # See conflicted files
# ... edit files to resolve ...
git add <resolved-files>
git rebase --continue
# 4. Push with force-with-lease
git push --force-with-lease origin ASP-XXX-feature
During PR Review (After Feedback)
# 1. Make requested changes
git add . && git commit -m "fix: address PR feedback [ASP-XXX]"
# 2. Fetch and rebase again
git fetch origin dev
git rebase origin/dev
# 3. Push update
git push --force-with-lease origin ASP-XXX-feature
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.
- 3d ago First seen · 286 lines · 62 tokens per session scan A 367a614d139b
git-advanced is a skill published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 1,584 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to git-advanced, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
semantic-szz-analyzer
Identify bug-introducing commits using semantic analysis that extends traditional SZZ algorithm. Distinguishes semantic changes from refactorings or code movements using control-flow and data-flow similarity analysis. Use when analyzing bug-fix commits to trace back to bug-introducing changes, investigating software…
szz-bug-introducing-commit-identifier
Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining…
magpie-setup-upstream-fix
Turn a framework bug or quirk the agent hit while running a Magpie skill or tool into a fix PR against apache/magpie — one PR per issue. First confirms the problem is a framework defect (not a local misconfiguration or a stale snapshot), then searches apache/magpie for an existing issue or PR that already covers it…