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 commands/nitinjain999/platform-skills/commitgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWhat 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.00074 | $0.01130 |
| Opus 5 | $0.00037 | $0.00565 |
| Sonnet 5 | $0.00015 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze changes and generate a Conventional Commits message explaining the motivation behind the change.
Mode: analyze
Inspect staged or unstaged changes and classify the commit type and scope.
Steps:
- Run
git diff --staged— if empty, rungit diff HEADto capture unstaged changes - Group changed files by logical concern (feature, fix, refactor, docs, config, tests, ci)
- Identify the type from the change pattern:
feat— new capability or behavior addedfix— corrects broken or incorrect behaviorrefactor— restructures code without changing behaviorperf— measurably improves performancetest— adds or corrects tests onlydocs— documentation onlychore— build tooling, dependency updates, config changes with no production effectci— changes to CI/CD pipelines or workflow filesrevert— reverting a prior commit
- Infer scope from the most specific common ancestor: module name, service name, directory, or filename
- Check for breaking changes: API removals, signature changes, config renames, behavior inversions — flag with
!and addBREAKING CHANGE:footer - Report: detected type, scope, whether breaking, and a one-line WHY summary
Reference: references/conventional-commits.md → Type Classification, Scope Rules
Mode: generate
Generate a complete conventional commit message from diff or description.
Steps:
- Run
analyzemode first to determine type, scope, and breaking status - Write the subject line:
- Format:
<type>(<scope>): <imperative verb> <what and why> - Max 72 characters
- Imperative mood: "add", "fix", "remove", "update", "extract" — not "added", "fixes"
- Focus on the WHY, not just the what: "fix(auth): validate token expiry before redirect" not "fix(auth): update token check"
- Format:
- Write the body (when the subject line is insufficient):
- Wrap at 72 characters
- Explain the problem being solved and the approach chosen
- One blank line between subject and body
- Write footers:
BREAKING CHANGE: <description>for breaking changes (also add!to subject)Fixes #<issue>orCloses #<issue>for linked issuesCo-authored-by:if applicable
- Output the full message in a code block ready to copy
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.
- 2d ago First seen · 106 lines · 74 tokens per session scan A 96a8a7fcbd9e
commit is a command published in the GitHub repository nitinjain999/platform-skills (40 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,130 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-08-30.
Other commands, from other repositories
quick-commit
Create a conventional commit with an auto-generated message.
fest-commit
Commit changes with festival traceability metadata.
commit-all
Group all changes semantically and commit each group separately.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
commit
智能生成 Git 提交信息并提交.