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 ayush-singh-0601/commit-discipline-mcp --skill assetsgit clone --depth 1 https://github.com/ayush-singh-0601/commit-discipline-mcpWrote 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/ayush-singh-0601/commit-discipline-mcp/assets)<a href="https://agentmods.dev/skills/ayush-singh-0601/commit-discipline-mcp/assets"><img src="https://agentmods.dev/badge/skills/ayush-singh-0601/commit-discipline-mcp/assets/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/ayush-singh-0601/commit-discipline-mcp/assets"><img src="https://agentmods.dev/badge/skills/ayush-singh-0601/commit-discipline-mcp/assets.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.00025 | $0.00154 |
| Opus 5.5 | $0.00010 | $0.00062 |
| Sonnet 5.5 | $0.00005 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
commit-discipline 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 2mo 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.
What it actually says
Commit Discipline
Use this skill for implementation work that should be split into reviewable commits.
- Before editing, call
plan_taskwith 2-4 ordered stages and exact repository-relative files. - Work only on the current stage's declared files.
- Call
commit_stagefor the current stage instead of runninggit commitdirectly. - Check
task_statusbefore moving to the next stage. - Call
finish_taskonly after every stage is committed and the worktree is clean.
Never use this tool to push, rewrite history, or bypass failing tests.
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.
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.
- 2mo ago First seen · 17 lines · 25 tokens per session scan A 9ea3027e7999
commit-discipline is a skill published in the GitHub repository ayush-singh-0601/commit-discipline-mcp (1 stars, last pushed 10d ago), licensed MIT. It adds 25 tokens to every session and 154 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
specflo-execute
Use at a specflo project's execute phase, when turning a validated plan.md into committed, verified code one task at a time. Triggers include "execute the plan", "start building", "work the next task", or specflo status showing the execute phase. Do NOT use before a plan has been validated, or for trivial fixes…
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
git-commit
Analyze changes with Git only and auto-generate conventional commit messages with optional emoji; suggests splitting commits when needed, runs local Git hooks by default (use --no-verify to skip).
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-master
MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog). Load it before running git yourself, or pass loadskills=['git-master'] to the task that commits. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.