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 skills add abdullahkhawer/devops-skills --skill commit-codegit clone --depth 1 https://github.com/abdullahkhawer/devops-skillsWrote 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/skills/abdullahkhawer/devops-skills/commit-code)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/commit-code"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/commit-code/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/skills/abdullahkhawer/devops-skills/commit-code"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/commit-code.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.00018 | $0.00820 |
| Opus 5.5 | $0.00007 | $0.00328 |
| Sonnet 5.5 | $0.00004 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
commit-code 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 28d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Code Skill
Run this skill when asked to commit code changes, create a commit message, or push changes to a new branch.
Step 1 — Collect input
Ask the user the following question:
Kindly let me know:
1. Branch Name: What should I name the new branch? (name of the branch)
If the user has already provided the answer upfront, skip the question and use the provided value.
Step 2 — Create a new branch
git checkout -b <BRANCH_NAME>
Step 3 — Run pre-commit checks (if .pre-commit-config.yaml exists)
pre-commit run -a
If the command fails, try again only one more time. If it fails again, report the output to the user and stop. Do not continue until the user resolves any failures.
Step 4 — Run Terraform formatting (if Terraform files exist)
terraform fmt -recursive
Step 5 — Stage all changes, analyze them and commit
git add .
Before proceeding, list the staged files and check for potentially sensitive files (e.g. .env, *.pem, *.key, *credentials*, *secret*, *token*, *password*):
git diff --cached --name-only
If any staged file matches a sensitive pattern, pause and ask the user to confirm whether it should be included in the commit. Do not proceed until confirmed.
And then analyze the code changes in each staged file with the following command:
git diff --cached -- <FILE_PATH>
Then based on all the code changes, determine the appropriate conventional commit type, compose a single one-liner commit message, and commit the changes with the following command:
git commit -m "<TYPE>: <COMMIT_MESSAGE>"
Commit message rules
- Single line only — no multi-line messages.
- Must be descriptive and mention all relevant changes.
- First letter of
<COMMIT_MESSAGE>must be capitalized. - NEVER include a scope — do NOT use
<TYPE>(scope): ...format, even if a Jira ticket or branch name is provided. - Examples:
fix: Fix memory leak in runner cleanup,feat: Add retry logic for failed jobs,feat!: Drop support for Node 16 - Reference: https://www.conventionalcommits.org/en/v1.0.0/
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.
- 28d ago Changed · +2 lines 11ef1c26af77
- 1mo ago First seen · 114 lines · 18 tokens per session scan A 886f34f02d86
commit-code is a skill published in the GitHub repository abdullahkhawer/devops-skills (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 18 tokens to every session and 820 once invoked, about $0.0001 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.
Other skills, from other repositories
git-hooks-setup
Use when setting up git hooks (pre-commit, commit-msg, pre-push) with husky or native hooks for linting, formatting, commit conventions, and secret scanning.
commit-conventions
Standards for writing clear and consistent commit messages using Conventional Commits format. Use when making git commits, reviewing commit history, creating pull requests, or when the user asks about commit message formatting, git workflows, or version control best practices.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.