Borrowing it
Nothing to install: this file belongs to nizovtsevnv/outline-mcp-rs. 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/nizovtsevnv/outline-mcp-rs/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/nizovtsevnv/outline-mcp-rsWrote 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/nizovtsevnv/outline-mcp-rs/commit)<a href="https://agentmods.dev/skills/nizovtsevnv/outline-mcp-rs/commit"><img src="https://agentmods.dev/badge/skills/nizovtsevnv/outline-mcp-rs/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/skills/nizovtsevnv/outline-mcp-rs/commit"><img src="https://agentmods.dev/badge/skills/nizovtsevnv/outline-mcp-rs/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.00016 | $0.00456 |
| Opus 5 | $0.00008 | $0.00228 |
| Sonnet 5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 10d 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
Semantic Commit
Collect all uncommitted changes and create a single structured commit.
Process
- Run
git status(without-uall) andgit diff(staged + unstaged) in parallel to understand changes - Run
git log --oneline -5for recent commit context - Analyze changes: which files are affected, what was added/removed, purpose of the changes
- Stage files by name (do not use
git add -A; never add.env, credentials, binary files) - Compose a commit message in conventional commits format:
feat(scope): description— new functionalityfix(scope): description— bug fixdocs(scope): description— documentationrefactor(scope): description— refactoring without behavior changeperf(scope): description— performance improvementtest(scope): description— testschore(scope): description— maintenance- Scope = affected crate or area (app, core, db, broker, i18n)
- If changes span multiple scopes — use the primary one or omit
- Commit body (after blank line) explains why, not what
- Commit messages in English
- Create the commit via HEREDOC. Never use
--no-verify. - If a pre-commit hook fails — fix the issue, re-stage and create a new commit (never
--amend) - Show
git statusafter the commit to confirm
Rules
- Never commit files containing secrets
- Never use
--no-verifyor--no-gpg-sign - Never amend without explicit request
- If there are no changes — report and stop
- Summary line up to 72 characters
- Communicate in the user's language
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.
- 10d ago First seen · 42 lines · 16 tokens per session scan A 66bb0bbbd705
commit is a skill published in the GitHub repository nizovtsevnv/outline-mcp-rs (7 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 456 once invoked, about $0.0001 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
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
docs-update
Use when documentation has drifted from code changes and the user asks to synchronize. Not for ADRs or architectural rationale (docs-and-adrs). Not for writing an isolated document (docs-writing).