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/hbarbosa02/alaz-mcp-nestjs/commit-patternnpx skills add hbarbosa02/alaz-mcp-nestjs --skill commit-patterngit clone --depth 1 https://github.com/hbarbosa02/alaz-mcp-nestjsWrote 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/hbarbosa02/alaz-mcp-nestjs/commit-pattern)<a href="https://agentmods.dev/skills/hbarbosa02/alaz-mcp-nestjs/commit-pattern"><img src="https://agentmods.dev/badge/skills/hbarbosa02/alaz-mcp-nestjs/commit-pattern.svg" alt="Measured on agentmods" 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.00069 | $0.00504 |
| Opus 5 | $0.00034 | $0.00252 |
| Sonnet 5 | $0.00014 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
commit-pattern 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 5d 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 pattern (project)
Canonical detail and examples: .cursor/rules/commit-pattern.mdc.
Workflow (every commit)
-
Run the gate (or ensure the local hook will pass):
npm run precommit- Hook:
core.hooksPath→.githooksruns the same ongit commitwhen configured (npm installrunsprepare).
- Hook:
-
Draft the message using Conventional Commits:
<type>(<optional-scope>): <imperative subject>- Types:
feat|fix|docs|style|refactor|test|chore|ci|perf|build - Subject: imperative, no trailing period, ≤ 72 characters
- Optional body after a blank line; optional footer:
BREAKING CHANGE:,Refs #id,Closes #id
- Types:
-
Before push — confirm: single logical change, no secrets or junk files, and update
README.md/docs/when user-visible behavior changed. For risky changes, also runnpm run test:e2e. -
If
precommitfails: usenpm run lint:fix,npm run format, fix tests, then recommit. Usegit commit --no-verifyonly in exceptional cases (hook skipped intentionally).
Anti-patterns (reject)
- Subjects like
WIP,update,fix stuff, or ticket-only lines - Subject ending with
. - Vague or mixed unrelated changes in one commit
Commands
| Goal | Command |
|---|---|
| Full local gate | npm run precommit |
| Lint fix | npm run lint:fix |
| Format | npm run format |
| Unit tests | npm test |
| E2E (when needed) | npm run test:e2e |
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.
- 5d ago First seen · 44 lines · 69 tokens per session scan A 7c6353c63a92
commit-pattern is a skill published in the GitHub repository hbarbosa02/alaz-mcp-nestjs (2 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 504 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
commit
Commit message formatting and guidelines.
commit
Create a git commit with optional automatic Linear issue linking. Use when the user asks to commit.