Borrowing it
Nothing to install: this file belongs to hhopke/intervals-icu-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/hhopke/intervals-icu-mcp/main/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/hhopke/intervals-icu-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/hhopke/intervals-icu-mcp/commit)<a href="https://agentmods.dev/skills/hhopke/intervals-icu-mcp/commit"><img src="https://agentmods.dev/badge/skills/hhopke/intervals-icu-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/skills/hhopke/intervals-icu-mcp/commit"><img src="https://agentmods.dev/badge/skills/hhopke/intervals-icu-mcp/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01639 |
| Opus 5.5 | $0.00018 | $0.00656 |
| Sonnet 5.5 | $0.00009 | $0.00328 |
| Haiku 4.5 | $0.00005 | $0.00164 |
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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Gather the following before composing the commit message:
- Current branch:
git branch --show-current - Working tree status:
git status --short --branch - Diff (staged + unstaged):
git diff $(git rev-parse --verify HEAD 2>/dev/null || echo --cached) - Recent history:
git log --oneline -10
Branch guard — MANDATORY first step
Never commit on main. Before staging or committing:
- Run
git branch --show-current. - If the result is
main:- Propose a branch name derived from the commit type/scope (e.g.
fix/hr-histogram-list-shape,feat/event-tags). - Confirm the name with the user, then
git switch -c <branch>. - Only then proceed to stage + commit.
- Propose a branch name derived from the commit type/scope (e.g.
- If on any other branch, commit there as-is — do not create a new branch.
No exceptions: trivial fixes, doc tweaks, one-liners — all go through a non-main branch.
Commit message rules
- Single line. No body. No
Co-Authored-By/ Claude attribution. This applies to every commit in this repo, regardless of size. - Format:
type(scope): description— Conventional Commits. - Types:
feat,fix,docs,style,refactor,test,chore,ci,build,perf. - Scope is optional but encouraged. Conventional scopes here:
tools,client,middleware,models,wellness,events,ci,release, or a specific tool module name. - Do not put issue refs (
Closes #N) in the commit message — those live in the PR body so GitHub auto-closes correctly on merge (and squash merges use a blank commit body, so commit-message refs would be dropped anyway).
Doc + count sync
For feat, fix, or anything user-visible, check whether docs need updating in the same commit:
CHANGELOG.md— add a bullet under## [Unreleased]. CHANGELOG is manual in this repo; nothing generates it. Group bullets under### Added/### Changed/### Fixedmatching the existing style.- Tool / resource / prompt counts — if tools were added or removed, update the counts that appear in:
README.md(header/intro line and any tool tables)CLAUDE.md(project overview line stating tool counts)docs/tools.mdif the registered set changed
- README discipline — keep
README.mdunder 300 lines. If a new section would push past ~30 lines and isn't core onboarding, extract it todocs/and link from the README. - SemVer flag — if the change removes or renames a tool/parameter, changes config env var semantics, changes default tool registration (e.g.
INTERVALS_ICU_DELETE_MODE), or removes information from a response, call it out in the PR body — this requires a major version bump per CLAUDE.md. Response-shape changes that preserve the information (key renames, restructuring, added fields) are minor, not breaking. - Do not reference upstream/comparison repos in commit messages, PR bodies, CHANGELOG, or README.
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 · 90 lines · 46 tokens per session scan A 8413e0fe2610
commit is a skill published in the GitHub repository hhopke/intervals-icu-mcp (109 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,639 once invoked, about $0.0002 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-30.
Other skills, from other repositories
repository-manager-bulk-git-operations
Bulk, parallel git operations across a whole workspace of repositories via the repository-manager MCP server — clone, pull, push, add, commit, pre-commit, phased push, and enumerate every repo across a GitLab instance / GitHub org into an ingest manifest (which also natively ingests them into the knowledge graph as…
bootstrap
Use when resolving Postman CLI setup, authentication, or a repository workspace binding; initializing local API files; handling a CLI error that says an operation isn't allowed because of insufficient entitlements; or importing, pulling, pushing, syncing, or sharing workspace resources. Reuses existing context and…
commit
Use when asked to commit, "commit this", "/commit", or to write a commit for the pending change — reviews what the change reaches outside its diff first, then commits with a message that names it.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
app_tagline_backfill
Give apps built on this instance a share-card tagline when their app.yaml has none. Runs automatically once after Rome upgrades (AUTO mode, list supplied by the caller) or on request from the guardian ("add taglines to my apps", MANUAL mode, confirm before writing). Only touches editable mode: "source" apps — never…