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.
git clone --depth 1 https://github.com/andrei-isvoran96/claude-skill-labWrote 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.
[](https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/commit)<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/commit"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/commit/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.
<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/commit"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00526 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
commit 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.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage, commit, and push changes to a new branch based on origin/<BASE_BRANCH>.
Arguments
This command accepts a branch name as $ARGUMENTS. Example: /commit bug/207-fix-disappearing-flow-lines
Steps
-
Validate the branch name. If
$ARGUMENTSis empty or blank, ask the user to provide a branch name and stop. Do NOT proceed without one. -
Fetch the latest
<BASE_BRANCH>from origin:git fetch origin <BASE_BRANCH> -
Check for staged/unstaged changes. Run
git statusandgit diff(both staged and unstaged) to understand what will be committed. If there are NO changes to commit (no modified, added, or deleted tracked files), inform the user and stop. -
Create the branch from
origin/<BASE_BRANCH>:git checkout -b $ARGUMENTS origin/<BASE_BRANCH>If the branch already exists locally, inform the user and ask whether to switch to it or abort.
-
Verify the changes carried over. Run
git statuson the new branch to confirm the working tree changes are present. Show the user a summary of what will be committed. -
Stage the relevant files. Only stage files that are related to the work — do NOT stage untracked files that look unrelated (test artifacts, temporary files,
.envfiles, credentials, etc.). When in doubt, ask the user which files to include. -
Draft a commit message by analyzing the staged diff:
- Follow conventional commits format (
fix:,feat:,refactor:,docs:,chore:, etc.) - Keep the subject line under 72 characters
- Add a body explaining the "why" if the change is non-trivial
- Use a HEREDOC to pass the message:
git commit -m "$(cat <<'EOF' fix: short description Longer explanation if needed. EOF )"
- Follow conventional commits format (
-
Push the branch to origin:
git push -u origin $ARGUMENTS
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.
- 1mo ago First seen · 53 lines · 0 tokens per session scan A 8ac667f3c683
commit is a command published in the GitHub repository andrei-isvoran96/claude-skill-lab (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 526 tokens. 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 commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.