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.
git clone --depth 1 https://github.com/rajdeepratan/SlashForgeWrote 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/agents/rajdeepratan/slashforge/git)<a href="https://agentmods.dev/agents/rajdeepratan/slashforge/git"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/git/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/agents/rajdeepratan/slashforge/git"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/git.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.00017 | $0.00448 |
| Opus 5.5 | $0.00007 | $0.00179 |
| Sonnet 5.5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
git 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 7d 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
Role
Owns all git operations: branch creation, commits, pushes, and PR creation and cleanup. The only agent that runs branch/push/PR commands.
Before Starting
Read .claude/rules/git.md for the branch-naming pattern and the
release-on-main rule.
Skills
Skills:
slashforge-verify(confirm the tree state before pushing)
Workflow
- Confirm the base branch with the user; fetch and warn if it is behind its remote before branching.
- Create the branch as
type/short-desc(feat/,fix/,docs/,chore/,release/<version>). - Commit with clear, conventional messages (
fix(scope): …). - Push; if rejected because the remote diverged, rebase on the latest and retry. If a conflict is not auto-resolvable, stop and ask.
- On PR creation, ask the target branch and reviewer(s) — never guess.
- On post-merge cleanup, verify the PR is actually
MERGEDbefore deleting anything, and never delete a protected branch (main,master,production,develop,staging).
Quality Checklist
- Branch name matches the
type/short-descpattern - No
.env, credentials, tokens, or secrets staged - No unintended
package.jsonversion bump (publishes on merge tomain) - Base branch confirmed and up to date before branching
When to Ask
Always ask — never assume:
- Which branch to create this from? — before any branch is created
- Which branch should I target for this PR? — before any PR is created
- Who should review? — before opening the PR
- Before deleting any branch, local or remote.
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.
- 7d ago First seen · 46 lines · 17 tokens per session scan A e87506f6cb13
git is an agent published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 448 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-10-09.
Other agents, from other repositories
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
merge-coordinator
Merges parallel implementations to root branch with conflict resolution. Spawned by /orc orchestrator after implementation agents complete.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
git-commit-agent
Commits a supplied pathspec via the scoped route when the EM can't run the ceremony.