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 agentmods add commands/javiermrcom/awesome-claude-code/git-statusgit clone --depth 1 https://github.com/javiermrcom/awesome-claude-codeWhat 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 | $0.00008 | $0.00474 |
| Opus 5 | $0.00004 | $0.00237 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
git-status 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.
What it actually says
Git Status
Analyze the current state of the git repository and provide a structured, actionable summary.
Commands to Execute
- Current Status: !
/usr/bin/git status - Current branch: !
/usr/bin/git branch --show-current - Current diff: !
/usr/bin/git diff HEAD origin/main - Recent commits: !
/usr/bin/git log --oneline -5 --pretty=format:"%h - %s" - Upstream status: !
/usr/bin/git status -sb
Files to Read
@README.md
Task
Based on the git commands output above, provide a structured summary in the following format:
📊 Repository Status
- Branch: {current_branch}
- Status: {clean/uncommitted changes/untracked files/conflicts}
- Upstream: {ahead X commits/behind Y commits/in sync/not tracking remote}
📝 Recent Activity
{List last 5 commits with commit hash and message} {Highlight any Linear issue references (IA-XXX) or Sentry references if present}
🔄 Pending Changes
- Staged: {count} files {list if < 5 files}
- Unstaged: {count} files {list if < 5 files}
- Untracked: {count} files {list if < 3 files}
📋 Summary of Changes
{Brief description of what's being worked on based on file changes and commit messages} {Identify the main area: feature, fix, refactor, docs, etc.}
⚠️ Recommendations
{Suggest next actions based on current state:}
- If uncommitted changes: "Run
/committo create a logical commit" - If ahead of origin: "Consider creating a PR with
/pr" - If clean state: "Ready to start new work or switch branches"
- If behind origin: "Pull latest changes before continuing"
- If untracked files: "Review and stage relevant files"
🔗 Related Context
{If Linear issues or Sentry errors detected in commits/branch, mention them}
Make the summary concise, actionable, and easy to scan.
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 · 56 lines · 8 tokens per session scan A e39cdd54fc2d
git-status is a command published in the GitHub repository javiermrcom/awesome-claude-code (3 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 474 once invoked, about $0.0000 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.