A release workflow for merging code into the main branch, assigning a version, and deploying it to production.

Use it to publish the main repository or a submodule, create planned or patch releases, and deploy completed work.

It organizes planned milestone releases separately from smaller ongoing updates and can target either the main project or a named subproject.

publish — Skill for Claude Code by markmhendrickson

Install

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.

Any agent

npx skills add markmhendrickson/neotoma --skill publish

Clone the repo

git clone --depth 1 https://github.com/markmhendrickson/neotoma

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/markmhendrickson/neotoma/publish.svg)](https://agentmods.dev/skills/markmhendrickson/neotoma/publish)

Your own site

<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/publish"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/publish.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 4,320 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Tool Misuse · line 430
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
high Tool Misuse · line 450
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
medium Agent Snooping · line 6
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

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.00003	$0.04320
Opus 5	$0.00002	$0.02160
Sonnet 5	$0.00001	$0.00864
Haiku 4.5	$0.00000	$0.00432

Measured 7d ago against content hash 637ea8a86251, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

publish — 100% identical, 7 lines differ

.claude/skills/publish/SKILL.md · 562 lines

How it starts

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

name: publish description: Publish workflow per foundation publish command. triggers:

publish
/publish

publish

Merge dev commits into main, create a release (planned or incremental), and deploy to production.

PARAMETER MODES:

No parameter (default): Publish main repository
Submodule name parameter (e.g., /publish foundation): Publish that specific submodule only

Release Numbering Strategy

Planned Releases (Milestones):

Use semantic versioning: vX.Y.0 (major.minor.0)
Examples: v1.0.0, v1.1.0, v2.0.0
Created via /create_release command with full workflow
Control major and minor version numbers

Incremental Releases (Continuous Deployments):

Use semantic versioning as patches: vX.Y.Z where Z increments
Examples: If last planned release is v1.1.0, incremental releases are v1.1.1, v1.1.2
Auto-generated via /publish command
Only patch version increments (never major or minor)

Relationship:

Independent purposes: Planned releases are milestones, incremental releases are continuous deployments
Example sequence: v1.0.0 (planned) → v1.0.1, v1.0.2 (incremental) → v1.1.0 (planned) → v1.1.1 (incremental)

Parameter Detection and Routing

STEP 1: Detect parameter and route to appropriate workflow:

# Check if parameter provided
if [ -n "$1" ]; then
  PARAM="$1"
  
  # Submodule mode: publish that submodule only
  echo "📦 SUBMODULE MODE: Publishing submodule '$PARAM'"
  # Verify submodule exists
  if ! git submodule status "$PARAM" >/dev/null 2>&1; then
    echo "❌ Submodule not found: $PARAM"
    exit 1
  fi
  # Proceed to submodule publish workflow
else
  # Main repo mode: publish main repository
  echo "📦 MAIN REPO MODE: Publishing main repository"
  # Proceed to main repository publish workflow
fi

Submodule Publish Workflow

When a specific submodule name is provided (e.g., /publish foundation):

Read the full file on GitHub · 562 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.

7d ago First seen · 562 lines · 3 tokens per session scan A 637ea8a86251

Subscribe to this mod's changes

publish is a skill published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed 4d ago), licensed MIT. It adds 3 tokens to every session and 4,320 once invoked, about $0.0000 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-30.

Git and workflow Releases agent-infrastructure agent-memory ai-agents deterministic-state entity-resolution event-sourcing

publish

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

publish

Release Numbering Strategy

Parameter Detection and Routing

Submodule Publish Workflow

What this file has done since we first saw it

Other skills, from other repositories

pr-body

github-ops

evolve-lite:publish

github-repo-management

gsd-ship

promote