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/vthinkdeveloper/vthink-agent-toolkit/commit-pushnpx skills add vthinkdeveloper/vthink-agent-toolkit --skill commit-pushgit clone --depth 1 https://github.com/vthinkdeveloper/vthink-agent-toolkitWhat 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.00055 | $0.01381 |
| Opus 5 | $0.00028 | $0.00691 |
| Sonnet 5 | $0.00011 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
commit-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 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit and Push
Overview
This skill handles the full commit-and-push workflow: stage changes, generate a meaningful commit message, get user approval on the message, commit, and push to the remote.
Workflow
Step 1: Assess the Current State
Run these commands in parallel to understand what needs to be committed:
git status— see staged, unstaged, and untracked files (never use-uall)git diff— see unstaged changesgit diff --cached— see already-staged changesgit log --oneline -5— see recent commit style for message consistencygit branch --show-current— identify the current branch
If there are no changes (nothing staged, no modifications, no untracked files), inform the user and stop.
Step 2: Stage Changes
- Stage all modified and new files relevant to the current work using
git addwith specific file paths. - Do NOT stage files that look like secrets or credentials (
.env,credentials.json,*.key,*.pem). If such files appear, warn the user and skip them. - Do NOT use
git add -Aorgit add .— always add specific files by name.
Step 3: Generate a Commit Message
Analyze the staged diff (git diff --cached) and draft a commit message following the Conventional Commits specification (https://www.conventionalcommits.org/en/v1.0.0/).
Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types
Choose the correct type based on the nature of the change:
| Type | When to use |
|---|---|
feat |
A new feature (correlates with SemVer MINOR) |
fix |
A bug fix (correlates with SemVer PATCH) |
docs |
Documentation-only changes |
style |
Formatting, whitespace, semicolons — no logic change |
refactor |
Code restructuring without fixing a bug or adding a feature |
perf |
Performance improvement |
test |
Adding or updating tests |
build |
Build system or external dependency changes |
ci |
CI configuration changes |
chore |
Maintenance tasks that don't modify src or tests |
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 · 157 lines · 55 tokens per session scan A e6c2331cb86c
commit-push is a skill published in the GitHub repository vthinkdeveloper/vthink-agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,381 once invoked, about $0.0003 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
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…