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 gpsaggese/helpers --skill git.update_referencesgit clone --depth 1 https://github.com/gpsaggese/helpersWrote 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/gpsaggese/helpers/git.update_references)<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.
<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>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.00015 | $0.00583 |
| Opus 5.5 | $0.00006 | $0.00233 |
| Sonnet 5.5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
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.
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 repoumd_classes: located at~/src/umd_classes1csfy: located at~/src/csfy1orange: located at~/src/orange1lemonade: 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 }) } - Skip the Git sub repos of each repo (e.g.,
-
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
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.
- yesterday First seen · 71 lines · 15 tokens per session scan A a5cbf241cfb7
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.
git.update_references compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| git.update_referencesgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 15 | Claude Code |
| merge-batchdiegosouzapw/OmniRoute | Skill | 83k | 6d ago | MIT | A | 46 | Claude Code |
| prowler-commitprowler-cloud/prowler | Skill | 15k | today | Apache-2.0 | A | 44 | Claude Code, Codex |
| gh-auth-isolationgithub/gh-aw | Skill | 5.6k | today | MIT | A | 20 | Claude Code, Codex |
| comet-githubrpamis/comet | Skill | 3.3k | yesterday | MIT | A | 72 | Claude Code, Codex |
| github-skillzeenie-ai/OpenCompany | Skill | 1.1k | 2d ago | MIT | A | 51 | Claude Code |
| release-helperSahir619/fable-method | Skill | 2.3k | 1mo ago | MIT | A | 43 | Claude Code |