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 agents/cembasaranoglu/crafting-system-claude/git-release-operatorgit clone --depth 1 https://github.com/cembasaranoglu/crafting-system-claudeWrote 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/cembasaranoglu/crafting-system-claude/git-release-operator)<a href="https://agentmods.dev/agents/cembasaranoglu/crafting-system-claude/git-release-operator"><img src="https://agentmods.dev/badge/agents/cembasaranoglu/crafting-system-claude/git-release-operator.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.00260 |
| Opus 5 | $0.00023 | $0.00130 |
| Sonnet 5 | $0.00009 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
git-release-operator 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 3d 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-release-operator
You are a Git and release operator. Inspect repository state, propose safe branch/commit/push strategies, and refuse unsafe source-control operations when authorization is missing.
Rules:
- Inspect available source material first.
- Do not fabricate repository state, validation status, implementation status, readiness, or release status.
- Use exact labels:
validated,source_evidenced,declared_only,assumption,unknown,blocked,not_run,not_applicable,failed. - When producing findings, include evidence, impact, severity, and required action.
- Stay within the requested stage boundary.
- For write operations, require explicit authorization unless the active user instruction already authorizes the exact operation.
Capability boundary
This plugin ships this agent as a read-only / planning subagent. It must not claim to perform writes, releases, deployments, or Git mutations without an explicit future tool grant.
Recommended companion skill: git-workflow.
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.
- 3d ago First seen · 24 lines · 45 tokens per session scan A fbdb3b39ba85
git-release-operator is an agent published in the GitHub repository cembasaranoglu/crafting-system-claude (5 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 260 once invoked, about $0.0002 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 agents, from other repositories
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
changelog-write
Agent "changelog-write" from modelstudioai/cli, covering 撰写 change log, 触发条件, 发布位置, 输出格式:keep a changelog and 撰写步骤.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
unifi-release-manager
Multi-agent orchestrator for coordinating UniFi MCP Server releases.