push

push is a skill for Claude Code, Codex from markmhendrickson/neotoma. It costs 3 tokens per session (1,846 once invoked), scanned A, original, MIT.

A command for sending the current Git branch to its remote repository, the shared copy hosted elsewhere. It checks the destination, branch, and unpushed commits first, and can work on a named Git submodule, a repository nested inside another repository.

In plain words
What is it for?
Use it to push the main repository or one submodule, verify the remote and branch, and handle push errors.
Why use it?
It catches common scope and setup problems before sharing changes, especially when a project contains separate nested repositories.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/markmhendrickson/neotoma/push
Any agent
npx skills add markmhendrickson/neotoma --skill push
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/neotoma

Made for: Claude Code, Codex.

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.

agentmods badge for push

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/neotoma/push.svg)](https://agentmods.dev/skills/markmhendrickson/neotoma/push)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/push"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/push.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 1,846 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00003 $0.01846
Opus 5 $0.00002 $0.00923
Sonnet 5 $0.00001 $0.00369
Haiku 4.5 $0.00000 $0.00185

Measured 3d ago against content hash 418864777e4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • push — 95% identical, 7 lines differ
.claude/skills/push/SKILL.md · 262 lines

How it starts

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


name: push description: Push current branch to origin; supports /push . triggers:

  • push
  • /push

push

Push current branch to origin remote, checking if remote exists first.

SUBMODULE MODE: If a submodule name is provided (e.g., /push foundation), scope operations to that submodule only, not the main repository.

Configuration is read from foundation-config.yaml.

If submodule name provided:

  1. Check if submodule exists: git submodule status <submodule-name>
  2. Change to submodule directory: cd <submodule-name>
  3. Run push workflow in submodule context
  4. Exit after submodule push (do NOT push main repository)

If no submodule name provided, proceed with main repository push workflow below.

Workflow Overview

  1. Check if origin remote exists
  2. Verify current branch
  3. Check for unpushed commits
  4. Push to origin
  5. Handle errors appropriately

Tasks

Step 1: Determine Scope

If submodule name provided:

  1. Verify submodule exists:

    if ! git submodule status <submodule-name> >/dev/null 2>&1; then
      echo "❌ Submodule not found: <submodule-name>"
      exit 1
    fi
    
  2. Save parent directory and change to submodule directory:

    ORIGINAL_DIR=$(pwd)  # Save parent directory before cd
    cd <submodule-name> || exit 1
    
  3. Update scope context (all subsequent operations in submodule)

If no submodule name provided, proceed with main repository context.

Step 2: Check if Origin Remote Exists

echo "🔍 Checking for origin remote..."

# Check if any remotes exist
if ! git remote | grep -q .; then
  echo "❌ Error: No git remotes configured"
  echo ""
  echo "To add a remote, run:"
  echo "  git remote add origin <remote-url>"
  echo "  git push -u origin <branch-name>"
  exit 1
fi

# Check specifically for origin remote
if ! git remote | grep -q "^origin$"; then
  echo "❌ Error: 'origin' remote not found"
  echo ""
  echo "Available remotes:"
  git remote -v
  echo ""
  echo "To add origin remote, run:"
  echo "  git remote add origin <remote-url>"
  echo "  git push -u origin <branch-name>"
  exit 1
fi

# Display origin URL
ORIGIN_URL=$(git remote get-url origin 2>/dev/null || echo "unknown")
echo "✅ Origin remote found: $ORIGIN_URL"

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

  1. 3d ago First seen · 262 lines · 3 tokens per session scan A 418864777e4f

Subscribe to this mod's changes

push is a skill published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed today), licensed MIT. It adds 3 tokens to every session and 1,846 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.

Related

Other skills, from other repositories

instar-session

Spawn, monitor, and communicate with persistent Claude Code sessions running in the background. Use when a task needs to run without blocking the current session, when the user asks to do something in the background, or when a long-running task needs its own context window. Trigger words: background task, spawn…

JKHeadley/instar · 79 tokens

install-hermes

One-click installation and configuration of Hermes Agent by Nous Research. Handles installing Hermes from scratch, adding LLM providers (OpenRouter, Anthropic, OpenAI, z.ai/GLM, Kimi, DeepSeek, Alibaba Qwen, Ollama, etc.), setting up messaging platforms (Telegram, Discord, Slack, DingTalk, Feishu/Lark, Weixin, WeCom)…

alibaba/anolisa · 124 tokens

shell-scripting

Use this skill when writing bash or zsh scripts, parsing arguments, handling errors, or automating CLI workflows. Triggers on bash scripting, shell scripts, argument parsing, process substitution, here documents, signal trapping, exit codes, and any task requiring portable shell script development.

alibaba/anolisa · 60 tokens

instar-scheduler

Schedule recurring agent tasks using cron expressions. Use when the user asks to run something on a schedule, check something periodically, automate a recurring task, set up a cron job, or wants work to happen while they're away. Trigger words: schedule, recurring, cron, every hour, every day, run daily, periodic…

JKHeadley/instar · 71 tokens

scheduling-tasks

Schedules reminders and recurring tasks via the letta cron CLI. Use when the user asks to be reminded of something, wants periodic work or check-ins, or needs to list, inspect, replace, or cancel scheduled tasks.

letta-ai/letta-code · 49 tokens

add-backend

Guide for adding a backend (Rust or Python) to the agent-sec-core security middleware. Use when creating new backends, integrating Rust or Python code into the security middleware, or extending with new backend actions.

alibaba/anolisa · 46 tokens