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.
curl -O https://raw.githubusercontent.com/PurdueRCAC/globus-mcp/main/.agents/skills/globus-publish/SKILL.mdgit clone --depth 1 https://github.com/PurdueRCAC/globus-mcpWrote 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/skills/purduercac/globus-mcp/globus-publish)<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.
<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>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 | $0.00041 | $0.01350 |
| Sonnet 5 | $0.00016 | $0.00540 |
| Haiku 4.5 | $0.00008 | $0.00270 |
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 10d 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.
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 intomainlocally, delete the branch (no remote PR).pr(default) → push branch + open a PR tomain.merge→ after opening the PR, alsogh pr merge --squash(only with explicit confirmation).
Safety Principles
- Base is
main. This repo has one long-lived branch; there is nodevelop. - Require a current approved review. If
TECH.mdreview.verdictis notapproved, STOP and report — proceed only on explicit human override. Approval is pinned toreview.last_reviewed_commit: any later commit touching anything outsidespec/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.mdkind: 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-Byon 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.
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.
- 10d ago First seen · 175 lines · 81 tokens per session scan A a68427364260
globus-publish is a skill published in the GitHub repository PurdueRCAC/globus-mcp (1 stars, last pushed 15d ago), licensed MIT. It adds 81 tokens to every session and 2,700 once invoked, about $0.0004 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.