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/claude-code-community-ireland/claude-code-resources/git-flowgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWhat 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.00017 | $0.00495 |
| Opus 5 | $0.00009 | $0.00247 |
| Sonnet 5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
git-flow 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 2d 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.
What it actually says
Git Flow Workflow
You are providing contextual git workflow assistance.
Steps
-
Detect current state: Run
git status,git branch, andgit log --oneline -5to understand the current git context. -
Determine action from
$ARGUMENTS:
branch — Create a properly named branch
- Ask for the purpose (feature, fix, hotfix, chore, docs, refactor)
- Ask for a short description or ticket number
- Create the branch with proper naming convention:
<type>/<ticket>-<description> - Example:
feature/PROJ-123-user-search
commit — Stage and commit with conventional message
- Run
git diffandgit diff --stagedto see changes - Analyze the changes to determine the commit type (feat, fix, refactor, docs, test, chore)
- Stage relevant files (prefer specific files over
git add -A) - Write a conventional commit message:
type(scope): description - Show the user the proposed commit for approval before executing
pr — Create a pull request
- Analyze all commits on the current branch vs main
- Run
git diff main...HEADto understand the full change - Generate a structured PR description (Summary, Motivation, Changes, Test Plan)
- Create the PR using
gh pr create
merge — Merge a branch safely
- Check if the branch is up to date with the target
- Run tests before merging
- Merge using the project's convention (squash, merge commit, or rebase)
- Clean up the branch after merge
conflict — Resolve merge conflicts
- Identify conflicting files with
git diff --name-only --diff-filter=U - For each conflicting file:
- Read both versions and understand the intent of each change
- Propose a resolution that preserves both intents
- Show the resolution to the user for approval
- After all conflicts are resolved, run tests to verify
- Execute: Carry out the chosen action with the user's approval.
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.
- 2d ago First seen · 51 lines · 17 tokens per session scan A a592d516bb93
git-flow is a command published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 495 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-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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.