Borrowing it
Nothing to install: this file belongs to AI-Riksarkivet/ra-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AI-Riksarkivet/ra-mcp/main/.claude/commands/commit.mdgit clone --depth 1 https://github.com/AI-Riksarkivet/ra-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/commands/ai-riksarkivet/ra-mcp/commit)<a href="https://agentmods.dev/commands/ai-riksarkivet/ra-mcp/commit"><img src="https://agentmods.dev/badge/commands/ai-riksarkivet/ra-mcp/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/ai-riksarkivet/ra-mcp/commit"><img src="https://agentmods.dev/badge/commands/ai-riksarkivet/ra-mcp/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.00445 |
| Opus 5.5 | $0.00000 | $0.00178 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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.
What it actually says
Help create a Conventional Commit following the specification (https://www.conventionalcommits.org/en/v1.0.0/).
First, run git status --short and git diff --cached --stat and git diff --stat to show current changes.
Then follow these rules for the commit format: [optional scope]:
[optional body]
[optional footer(s)]
RULES:
- Type is REQUIRED (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert)
- Scope is OPTIONAL - noun describing codebase section in parentheses
- Description is REQUIRED - short summary in imperative present tense
- Breaking changes indicated by:
- ! after type/scope (e.g., feat!: or feat(api)!:)
- OR BREAKING CHANGE: in footer
- Body is OPTIONAL - detailed explanation (blank line after description)
- Footer is OPTIONAL - uses format: token: value or BREAKING CHANGE: description
IMPORTANT INSTRUCTIONS:
- Do NOT add any co-author information
- Do NOT add "Generated with Claude Code"
- Do NOT add robot emojis or any Claude attribution
- Keep commit messages clean and professional
- Use lowercase for type and scope
- No period at end of description
- Description should be imperative: "add" not "added" or "adds"
WORKFLOW:
- Analyze the changes shown above
- Stage appropriate files with git add
- Create commit with git commit -m (for single line) or heredoc for multiline
- For multiline commits with body/footer, use:
OR use heredoc:git commit -m "type(scope): description" -m "" -m "body" -m "" -m "footer"git commit -F- <<'END' type(scope): description body paragraph footer: value END
Please analyze the changes and create an appropriate Conventional Commit.
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 · 51 lines · 0 tokens per session scan A 4e52bb7a4983
commit is a command published in the GitHub repository AI-Riksarkivet/ra-mcp (27 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 445 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-30.
Other commands, from other repositories
changelog
Generate a structured changelog from recent git commits, categorized by change type.
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
devkit.github.create-pr
Creates a GitHub pull request with branch creation, commits, and detailed description. Use when you need to submit changes for review.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.