git.update_references

git.update_references is a skill for Claude Code from gpsaggese/helpers. It costs 15 tokens per session (583 once invoked), scanned A, original, Apache-2.0.

A cross-repository reference updater that looks for files changed in one Git repository and finds references to them in other repositories.

In plain words
What is it for?
Use it to search specified related repositories for references to changed files and report the affected functions and paths.
Why use it?
It helps prevent other codebases from continuing to point to files or functions that were moved, renamed, changed, or deleted.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths; positional $N argument.

Good fit Use it to search specified related repositories for references to changed files and report the affected functions and paths.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/git.update_references
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 gpsaggese/helpers --skill git.update_references
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/git.update_references"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/git.update_references.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 583 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.00015 $0.00583
Opus 5.5 $0.00006 $0.00233
Sonnet 5.5 $0.00003 $0.00117
Haiku 4.5 $0.00002 $0.00058

Measured yesterday against content hash a5cbf241cfb7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git.update_references 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 yesterday.

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/skills/git.update_references/SKILL.md · 71 lines

How it starts

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

Goal

  • Find files moved, renamed, updated, or deleted in the current repo and update all references to them in the other Git repos

Workflow

Find Changed Files

  • Find all files moved, renamed, updated, or deleted in the current repo:

    > invoke git_files --branch --only-print-files
    
  • Print the files that are moved, renamed, or deleted

    • Print the main functions changed

Search for References

  • For each file <FILE>, search for its references in these repos:

    • helper: the current repo
    • umd_classes: located at ~/src/umd_classes1
    • csfy: located at ~/src/csfy1
    • orange: located at ~/src/orange1
    • lemonade: located at ~/src/lemonade1
  • You must:

    • Skip the Git sub repos of each repo (e.g., helpers_root)
    • Search only files under Git control
    • Skip symlinks (e.g., .claude) using an approach like:
    search_repo() {
      local repo_path=$1
      local search_term=$2
    
      (cd "$repo_path" && {
        # Get submodule paths to exclude
        submodules=$(git config --file .gitmodules --name-only --get-regexp path 2>/dev/null | sed 's/.*path=//' | tr '\n' '|' | sed 's/|$//')
    
        if [ -n "$submodules" ]; then
          git ls-files | grep -v "^($submodules)" | while read -r file; do
            [ ! -L "$file" ] && echo "$file"
          done | xargs grep "$search_term" 2>/dev/null
        else
          git ls-files | while read -r file; do
            [ ! -L "$file" ] && echo "$file"
          done | xargs grep "$search_term" 2>/dev/null
        fi
      })
    }
    
  • Print the references in a table organized by:

    • Repos
    • Files
  • Create a vim quickfile cfile for the locations using the conventions in .claude/skills/cfile.rules.md

  • Pause and ask the user to continue

Update References

  • Update the references in all the repos

Verification

  • Confirm every reference to each moved, renamed, or deleted file was updated in every repo
  • Re-run the search and confirm no stale reference remains

Read the full file on GitHub · 71 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. yesterday First seen · 71 lines · 15 tokens per session scan A a5cbf241cfb7

Subscribe to this mod's changes

git.update_references is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 583 once invoked, about $0.0001 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-11-06.

Related

git.update_references compared with skills from other repositories

git.update_references next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
git.update_referencesgpsaggese/helpersSkill158todayApache-2.0A15Claude Code
merge-batchdiegosouzapw/OmniRouteSkill83k6d agoMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15ktodayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6ktodayMITA20Claude Code, Codex
comet-githubrpamis/cometSkill3.3kyesterdayMITA72Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1k2d agoMITA51Claude Code
release-helperSahir619/fable-methodSkill2.3k1mo agoMITA43Claude Code