gss-scan

gss-scan is a command for Claude Code from sfc-gh-eraigosa/dotfiles. It costs 16 tokens per session (128 once invoked), scanned A, original, Apache-2.0.

A command that scans a directory for Git repositories with pending work. It reports uncommitted changes and whether repositories are ahead of, behind, or different from their remote branches.

In plain words
What is it for?
Use it to check a Git folder before maintenance, review local and remote differences, and identify repositories that need commits or syncing.
Why use it?
It gives you one summary of repositories needing attention without changing or synchronizing any files.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to check a Git folder before maintenance, review local and remote differences, and identify repositories that need commits or syncing.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sfc-gh-eraigosa/dotfiles/gss-scan
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.

Clone the repo
git clone --depth 1 https://github.com/sfc-gh-eraigosa/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 gss-scan

README.md
[![agentmods](https://agentmods.dev/badge/commands/sfc-gh-eraigosa/dotfiles/gss-scan/github.svg)](https://agentmods.dev/commands/sfc-gh-eraigosa/dotfiles/gss-scan)
Your own site
<a href="https://agentmods.dev/commands/sfc-gh-eraigosa/dotfiles/gss-scan"><img src="https://agentmods.dev/badge/commands/sfc-gh-eraigosa/dotfiles/gss-scan/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 gss-scan

Your own site · 80×15
<a href="https://agentmods.dev/commands/sfc-gh-eraigosa/dotfiles/gss-scan"><img src="https://agentmods.dev/badge/commands/sfc-gh-eraigosa/dotfiles/gss-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 128 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.00016 $0.00128
Opus 5 $0.00008 $0.00064
Sonnet 5 $0.00003 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured 9d ago against content hash 71f93291e175, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

gss-scan 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 9d 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.

ai/claude/commands/gss-scan.md · 15 lines

What it actually says

Scan for repositories that need attention.

Scan results

!gss scan ${ARGUMENTS:-$HOME/git}


Arguments: $ARGUMENTS

For each dirty repo above, summarize what kind of change is pending (uncommitted, unpushed, ahead/behind). Don't take action — just report. If the user wants to sync any of them, hand off to the git-safe-sync skill which requires explicit confirmation per repo.

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. 9d ago First seen · 15 lines · 16 tokens per session scan A 71f93291e175

Subscribe to this mod's changes

gss-scan is a command published in the GitHub repository sfc-gh-eraigosa/dotfiles (46 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 128 once invoked, about $0.0001 per session on Opus 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.