agentmods.dev

git-pull

git-pull is a skill for Claude Code from aiya000/dotfiles. It costs 39 tokens per session (708 once invoked), scanned A, original, MIT.

A Git workflow for safely bringing commits from a remote repository into the current branch. Git is the version-control system that records code changes and lets branches be synchronized.

In plain words
What is it for?
Use it when updating or synchronizing a branch with its remote. It fetches first, chooses an appropriate integration method, and reports the resulting changes.
Why use it?
It checks what is incoming and whether local work is uncommitted before changing the branch. When branches have diverged, it asks whether to rebase, merge, or cancel.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions AGENTS.md.

not rated 21repo 2d ago A scan 39 tokens original MIT

Good fit Use it when updating or synchronizing a branch with its remote. It fetches first, chooses an appropriate integration method, and reports the resulting changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aiya000/dotfiles/git-pull
View source ↗ aiya000/dotfiles
Install

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.

Any agent
npx skills add aiya000/dotfiles --skill git-pull
Clone the repo
git clone --depth 1 https://github.com/aiya000/dotfiles

Made for: Claude Code.

Wrote 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.

agentmods badge for git-pull

README.md
[![agentmods](https://agentmods.dev/badge/skills/aiya000/dotfiles/git-pull/github.svg)](https://agentmods.dev/skills/aiya000/dotfiles/git-pull)
Your own site
<a href="https://agentmods.dev/skills/aiya000/dotfiles/git-pull"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/git-pull/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.

agentmods 80×15 button for git-pull

Your own site · 80×15
<a href="https://agentmods.dev/skills/aiya000/dotfiles/git-pull"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/git-pull.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 708 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00708
Opus 5.5 $0.00016 $0.00283
Sonnet 5.5 $0.00008 $0.00142
Haiku 4.5 $0.00004 $0.00071

Measured 18d ago against content hash 2acbba4a66f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-pull 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 18d 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.

.claude_global/skills/git-pull/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

git-pull

Pull commits from remote after reviewing what is incoming and making sure local work is safe.

Behavior

  1. Run the git-fetch skill to fetch and learn the state of the branch against its upstream
  2. If the branch is up to date or only ahead, report that there is nothing to pull and stop
  3. Run git status to check for uncommitted changes (see Uncommitted Changes below)
  4. Decide how to integrate (see Choosing How to Integrate below)
  5. Pull, then run git status and report what changed, including anything git-fetch pointed out as running code or changing how tools behave

Choosing How to Integrate

  • Behind (fast-forward possible) -- run git pull --ff-only
  • Diverged -- do not pull yet. Use AskUserQuestion to present these options:
    • "Rebase" -- run git pull --rebase
    • "Merge" -- run git pull --no-rebase
    • "Cancel" -- abort without further action

If the project's AGENTS.md, or the user, says which one to use, follow that instead of asking.

Uncommitted Changes

If git status shows uncommitted changes, check whether any of them are in files the incoming commits touch (the files git-fetch reported).

  • No overlap -- proceed; git carries the changes across
  • Overlap -- do not pull. Use AskUserQuestion to present these options:
    • "Stash, pull, then pop" -- git stash push, pull, then git stash pop; report any conflict from the pop
    • "Commit first" -- cancel so the user (or the git-commit skill) can commit the changes first
    • "Cancel" -- abort without further action

Conflicts

If the pull stops with conflicts, do not resolve them on your own and do not abort the merge or rebase. List the conflicted files (git status) and ask the user how to proceed.

Does Not

  1. Run git reset --hard, git clean, git checkout -- <file>, or anything else that discards local changes
  2. Run git merge --abort or git rebase --abort without explicit user request
  3. Pull into a worktree this session was not launched in -- it changes the branch under whoever is working there
  4. Pull a branch other than the current one's upstream without explicit user request

Read the full file on GitHub · 59 lines

Changes

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.

  1. 18d ago First seen · 59 lines · 39 tokens per session scan A 2acbba4a66f1

Subscribe to this mod's changes

git-pull is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 708 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-09-28.

Git and workflowclojuredotfilesneovimvimxmonad
Related

Other skills, from other repositories

restart__pull_request

A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.

shunsock/dotfiles · 159 tokens

rescue__pull_request_review

An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.

shunsock/dotfiles · 104 tokens

submit__pull_request

An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.

shunsock/dotfiles · 100 tokens

write__pull_request

A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.

shunsock/dotfiles · 148 tokens

monitor__ci_status

An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.

shunsock/dotfiles · 116 tokens

monitor__pull_request_conflict

An automated check for GitHub pull requests, which are proposed code changes awaiting review or merging.

shunsock/dotfiles · 123 tokens