phantom-neural-cortex: Skill for Claude Code

.claude/skills/git-pushing/SKILL.md

git-pushing is a skill for Claude Code from LEEI1337/phantom-neural-cortex. It costs 70 tokens per session (742 once invoked), scanned A, original, MIT.

A workflow for staging, committing, and pushing Git changes to a remote repository, such as GitHub.

In plain words
What is it for?
Use it when you want to commit and push changes, including generating conventional commit messages and showing a pull-request link when available.
Why use it?
It removes the repetitive work of checking changes, writing a commit message, handling branches, and sending the work to the remote repository.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is LEEI1337/phantom-neural-cortex's own configuration. It tells Claude Code how to work on phantom-neural-cortex itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything phantom-neural-cortex configures →

Reuse

Borrowing it

Nothing to install: this file belongs to LEEI1337/phantom-neural-cortex. 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/LEEI1337/phantom-neural-cortex/master/.claude/skills/git-pushing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/LEEI1337/phantom-neural-cortex

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.

agentmods badge for git-pushing

README.md
[![agentmods](https://agentmods.dev/badge/skills/leei1337/phantom-neural-cortex/git-pushing/github.svg)](https://agentmods.dev/skills/leei1337/phantom-neural-cortex/git-pushing)
Your own site
<a href="https://agentmods.dev/skills/leei1337/phantom-neural-cortex/git-pushing"><img src="https://agentmods.dev/badge/skills/leei1337/phantom-neural-cortex/git-pushing/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.

agentmods 80×15 button for git-pushing

Your own site · 80×15
<a href="https://agentmods.dev/skills/leei1337/phantom-neural-cortex/git-pushing"><img src="https://agentmods.dev/badge/skills/leei1337/phantom-neural-cortex/git-pushing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 742 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.00742
Opus 5.5 $0.00028 $0.00297
Sonnet 5.5 $0.00014 $0.00148
Haiku 4.5 $0.00007 $0.00074

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

Security

Grade A, and why

git-pushing 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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/smart_commit.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/git-pushing/SKILL.md · 115 lines

How it starts

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

Git Push Workflow

Stage all changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

  • Explicitly asks to push changes ("push this", "commit and push")
  • Mentions saving work to remote ("save to github", "push to remote")
  • Completes a feature and wants to share it
  • Says phrases like "let's push this up" or "commit these changes"

Workflow

Fast Path (Recommended)

Use the automated script for maximum speed:

bash scripts/smart_commit.sh

This script handles:

  • ✅ Staging all changes
  • ✅ Auto-generating conventional commit messages
  • ✅ Adding Claude Code footer
  • ✅ Pushing to remote (with -u for new branches)
  • ✅ Showing PR link for GitHub repos

With custom message:

bash scripts/smart_commit.sh "feat: add new feature"

The script automatically:

  • Determines commit type (feat/fix/docs/test/chore/refactor)
  • Extracts scope from changed files
  • Handles new vs existing branches
  • Shows colored output for better UX

Manual Path (Fallback)

Use when script is unavailable or custom workflow needed:

1. Check Git Status

Run git status to understand:

  • Which files have changed
  • What will be committed
  • Current branch name

2. Stage Changes

  • Run git add . to stage all changes
  • Alternatively, stage specific files if partial commit is needed

3. Create Commit Message

If user provided a message:

  • Use it directly

If no message provided:

  • Analyze changes using git diff
  • Generate a conventional commit message:
    • Format: type(scope): description
    • Types: feat, fix, refactor, docs, test, chore
    • Keep description concise (50-90 characters)
    • Use imperative mood: "Add" not "Added"
  • Always append Claude Code footer:
    🤖 Generated with [Claude Code](https://claude.com/claude-code)
    
    Co-Authored-By: Claude <[email protected]>
    

Use heredoc format:

git commit -m "$(cat <<'EOF'
commit message here

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
EOF
)"

Read the full file on GitHub · 115 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 115 lines · 70 tokens per session scan A cf928f288f3e

Subscribe to this mod's changes

git-pushing is a skill published in the GitHub repository LEEI1337/phantom-neural-cortex (5 stars, last pushed 7mo ago), licensed MIT. It adds 70 tokens to every session and 742 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.