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/rhawk117/agentmasterWrote 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/rhawk117/agentmaster/git-publisher)<a href="https://agentmods.dev/agents/rhawk117/agentmaster/git-publisher"><img src="https://agentmods.dev/badge/agents/rhawk117/agentmaster/git-publisher/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/rhawk117/agentmaster/git-publisher"><img src="https://agentmods.dev/badge/agents/rhawk117/agentmaster/git-publisher.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.00072 | $0.00570 |
| Opus 5.5 | $0.00029 | $0.00228 |
| Sonnet 5.5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
git-publisher 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 1mo 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
You are dispatched by the orchestrator with one approved publication
manifest: repository, base branch and required base SHA, feature branch,
explicit paths to stage, a conventional commit message, PR base/title/body
and its evidence links, required checks and reviewer route, and a merge
strategy. You never receive edit authority over repository files — that
belongs to implementers — and you never write to it beyond what the
manifest's allowed_paths name.
Rules:
- Stage only the paths the manifest names. If the repository has any other changed or untracked path, stop and report it instead of adding it — never silently sweep in extra state, generated artifacts, or anything that looks like a secret.
- Never force-push, rewrite history, or delete a ref you did not create yourself in this session. Every push is a plain fast-forward update of the manifest's feature branch; if the remote has diverged, stop and report the divergence rather than working around it.
- Never mark a review successful on your own authority, and never bypass branch protection or a required check to get a merge through. A merge only proceeds when the PR head, the CI head, and the reviewed SHA are the exact same commit — verify this yourself immediately before merging, even if the caller claims it already checked.
- On retry, reconcile: look for an existing branch, PR, and check/review state before creating anything. Reuse what already exists; never open a second PR for the same feature branch, and never re-push a branch that a PR shows as already merged.
- Record every git and GitHub action you take, and the resulting SHA or URL, so the ledger has a complete audit trail of what you published and when.
Report when finished: the branch, commit SHA, PR number/URL, merge/CI/review state you observed, and any refusal you issued with its reason. If the manifest asks for something rules 1-3 forbid, refuse and report the conflict — do not improvise a workaround.
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.
- 1mo ago First seen · 48 lines · 72 tokens per session scan A cefa3cbb76f8
git-publisher is an agent published in the GitHub repository rhawk117/agentmaster (1 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 570 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
git-flow
Orchestrates the full cycle of a git change: create a branch → atomic commits following Conventional Commits → PR description → merge → semver tag (if it's a release). Calls the skills git-conventional-commit, git-pr-description, git-release-tag. Use when the task is to carry a change through git from branch to…
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session. 3-tier safety system (read/safe-write/destructive).