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.
npx agentmods add skills/jimmypaolini/codebase/submit-changesnpx skills add JimmyPaolini/codebase --skill submit-changesgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWhat 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 | $0.00077 | $0.01949 |
| Opus 5 | $0.00039 | $0.00975 |
| Sonnet 5 | $0.00015 | $0.00390 |
| Haiku 4.5 | $0.00008 | $0.00195 |
Grade A, and why
submit-changes 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit Changes
This skill automates the full pipeline from local changes to an open pull request: branch → commit → push → PR. Each phase is idempotent — already-completed steps are skipped automatically.
When to Use This Skill
- Submitting local changes as a complete workflow in one step
- Automating the branch + commit + PR process without manual intervention
- Shipping finished work without manually running each git command
Safety Rules
These rules are non-negotiable:
- NEVER run destructive commands (
git reset,git clean,git checkout -- .,git push --force,git rebase) - NEVER bypass hooks with
--no-verify - NEVER disable signing with
--no-gpg-sign - NEVER auto-fix pre-commit failures — report the failure and stop
- On any failure: report the error and stop immediately
Automatic Change Analysis
Before executing any phases, analyze the working tree and staged changes:
git status --porcelain
git diff HEAD
From the diff, automatically determine:
- Type — From the allowed types (see commit-code skill)
- Scope — From the allowed scopes (see commit-code skill)
- Gitmoji — Best-fit emoji for the type and intent (see commit-code skill)
- Subject — Concise imperative phrase, lowercase, no period, under 70 chars
These values drive the branch name, commit message, and PR title throughout all phases.
Phase 1 — Branch
-
Check current branch:
git rev-parse --abbrev-ref HEAD -
If on
main, create and switch to a new branch following checkout-branch conventions:git checkout -b <type>/<scope>-<description> -
Validate branch-name conformance for the current branch:
pnpm exec validate-branch-name -t "<branch>" -
If validation fails, run the rename-branch skill to derive and apply a compliant branch name, then re-run validation.
-
Push to remote and set upstream:
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.
- yesterday First seen · 176 lines · 77 tokens per session scan A 609c4aa3d6af
submit-changes is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,949 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…