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 alivirgo/Major-AI-Skills --skill abbreviated-git-statusgit clone --depth 1 https://github.com/alivirgo/Major-AI-SkillsWrote 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/alivirgo/major-ai-skills/abbreviated-git-status)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/abbreviated-git-status"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/abbreviated-git-status/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/alivirgo/major-ai-skills/abbreviated-git-status"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/abbreviated-git-status.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.00031 | $0.01511 |
| Opus 5 | $0.00015 | $0.00756 |
| Sonnet 5 | $0.00006 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
abbreviated-git-status scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Abbreviated Git Status Inspection (git status -s / --porcelain)
Overview
When an autonomous coding assistant executes a standard git status command, Git emits 30 to 80 lines of conversational advice ("On branch main", "Your branch is up to date with 'origin/main'", "use 'git add ...' to include in what will be committed", etc.).
In multi-turn agent loops with frequent state checks, this verbose commentary consumes 500 to 1,500 wasted tokens per turn without adding any actionable file-level information.
The Abbreviated Git Status Protocol enforces the use of git status -s (short format) or git status --porcelain=v1 / v2 - streaming a compact, machine-parseable 2-character matrix that reduces token consumption by 85% while retaining 100% of staging, modification, and branch tracking information.
Verbose vs. Short-Format Token Consumption
┌─────────────────────────────────────────────────────────────┐
│ Git Status Output Comparison │
│ │
│ Standard `git status` (Verbose ~450 tokens): │
│ On branch staging │
│ Your branch is up to date with 'origin/staging'. │
│ Changes to be committed: │
│ (use "git restore --staged <file>..." to unstage) │
│ modified: src/api/auth.ts │
│ Changes not staged for commit: │
│ (use "git add <file>..." to update what will be commit) │
│ modified: src/components/Header.tsx │
│ Untracked files: │
│ (use "git add <file>..." to include in what will commit) │
│ src/utils/token.ts │
│ │
│ Abbreviated `git status -s` (~45 tokens - 90% Reduction): │
│ M src/api/auth.ts │
│ M src/components/Header.tsx │
│ ?? src/utils/token.ts │
└─────────────────────────────────────────────────────────────┘
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 Changed · -6 tokens per session 43d39b76379a
- 12d ago First seen · 143 lines · 37 tokens per session scan A 2e64d10fe149
abbreviated-git-status is a skill published in the GitHub repository alivirgo/Major-AI-Skills (1 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,511 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
address-github-comments-v2
Address GitHub Comments workflow skill. Use this skill when the user needs you need to address review or issue comments on an open GitHub Pull Request using the gh CLI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
address-github-comments
Address GitHub Comments workflow skill. Use this skill when the user needs you need to address review or issue comments on an open GitHub Pull Request using the gh CLI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.