What is globus-publish?

A release step for moving an approved code branch into the project's main branch, either through a GitHub pull request or a local merge.

Use it to squash changes into main, open a documented pull request, or merge locally and remove the finished branch.

It provides a controlled final step after review and asks for confirmation before pushing changes or opening a pull request.

How PurdueRCAC/globus-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to PurdueRCAC/globus-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/PurdueRCAC/globus-mcp/main/.agents/skills/globus-publish/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/PurdueRCAC/globus-mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/purduercac/globus-mcp/globus-publish/github.svg)](https://agentmods.dev/skills/purduercac/globus-mcp/globus-publish)

Your own site

<a href="https://agentmods.dev/skills/purduercac/globus-mcp/globus-publish"><img src="https://agentmods.dev/badge/skills/purduercac/globus-mcp/globus-publish/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/purduercac/globus-mcp/globus-publish"><img src="https://agentmods.dev/badge/skills/purduercac/globus-mcp/globus-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,700 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00081	$0.02700
Opus 5.5	$0.00032	$0.01080
Sonnet 5.5	$0.00016	$0.00540
Haiku 4.5	$0.00008	$0.00270

Measured 2mo ago against content hash a68427364260, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

globus-publish 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 2mo 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.

.agents/skills/globus-publish/SKILL.md · 175 lines

How it starts

The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.

globus-publish — ship the branch to main

When to Use

Invoke /globus-publish once /globus-review has approved the branch (TECH.md review.verdict: approved). This is the one irreversible step — remote pushes and PRs can't be checkpointed — so it always confirms with you before acting. Default is a PR to main; local does a local squash-merge.

Harness portability. Runs on any harness — see factory/portability.md. Fallbacks: run the Current state commands yourself if not auto-injected; ask in plain text and STOP if AskUserQuestion is unavailable. gh/git are portable shell.

User Instructions

Additional instructions provided with the invocation: $ARGUMENTS

Current state (injected at load)

Branch: !git branch --show-current
Verdict / kind / slug: resolved in Step 1 from spec/{slug}/TECH.md (a load-time injection can't strip the branch prefix to form {slug}).
Commits vs main: !git log --oneline main..HEAD 2>/dev/null | head -n 30
Default remote branch: !gh repo view --json defaultBranchRef -q .defaultBranchRef.name 2>/dev/null || echo "(gh unavailable)"

Argument Parsing

local / no fuss → squash-merge into main locally, delete the branch (no remote PR).
pr (default) → push branch + open a PR to main.
merge → after opening the PR, also gh pr merge --squash (only with explicit confirmation).

Safety Principles

Base is main. This repo has one long-lived branch; there is no develop.
Require a current approved review. If TECH.md review.verdict is not approved, STOP and report — proceed only on explicit human override. Approval is pinned to review.last_reviewed_commit: any later commit touching anything outside spec/ invalidates it (the review's own artifact commit and meta-notes do not) — the Step 1 staleness gate checks this mechanically.
Confirm before irreversible/outward actions. Always confirm the mode, PR title, and body with the human (AskUserQuestion) before git push / gh pr create / local merge.
Squash-only. Do not create merge commits or rebase-merge, even though the repo's GitHub settings currently permit them. The PR title becomes the squash commit subject on main, so the PR title is [category] Imperative summary (category = TECH.md kind: feature|fix|refactor|docs|…) — never Conventional Commits (feat:/fix:).
Link, don't quote. The PR body references artifacts via SHA-pinned blob permalinks, not pasted copies.
No Co-Authored-By on any commit. PR bodies end with the Claude Code generation line.
Publish ships code, not releases. Version bumps and tags are /globus-release's job.

Read the full file on GitHub · 175 lines

Changes

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.

2mo ago First seen · 175 lines · 81 tokens per session scan A a68427364260

Subscribe to this mod's changes

globus-publish is a skill published in the GitHub repository PurdueRCAC/globus-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 2,700 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.

Git and workflow Releases

globus-publish next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
globus-publishPurdueRCAC/globus-mcp	Skill	2	2mo ago	MIT	A	81	Claude Code
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	yesterday	Apache-2.0	A	22	Claude Code, Codex

globus-mcp: Skill for Claude Code