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 skills add gtapps/hermitd --skill commitgit clone --depth 1 https://github.com/gtapps/hermitdWrote 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/gtapps/hermitd/commit)<a href="https://agentmods.dev/skills/gtapps/hermitd/commit"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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/gtapps/hermitd/commit"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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.00090 | $0.01283 |
| Opus 5.5 | $0.00036 | $0.00513 |
| Sonnet 5.5 | $0.00018 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- commit — 86% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Detect which plugin's scope this change belongs to, append a changelog line in that plugin's CHANGELOG, then commit. No push, no tag, no version bump — that's /release's job.
Guardrails (check before starting)
- Clean tree (
git statusshows nothing) → stop and say so, nothing to commit. - Detached HEAD, mid-rebase, or mid-merge → stop and ask the user to resolve that first.
- Never
--amend,--no-verify, force-push, or create tags here. - Never use
git add -Aorgit add .— staging is path-scoped per step 0. - If a pre-commit hook fails, fix the root cause and create a new commit — don't bypass the hook.
mainis the default base for everyday work. Claude Code's/plugin updateonly fires whenversioninplugin.jsonchanges, so commits merged tomainbetween releases are invisible to operators on the standard install path —[Unreleased]accumulates until/releaseships them.
Steps
0. Detect scope
Run git status --porcelain and partition the changed paths:
- Paths matching
plugins/<X>/...→ group by<X>(the slug). - Paths outside
plugins/(root README,.github/,.claude/,.claude-plugin/marketplace.json, root configs) → "root-scope" paths.
Then decide:
- Single plugin slug, no root-scope paths → set
$PLUGIN_DIR = plugins/<slug>/, set$SCOPE = plugin. Continue. - Multiple plugin slugs touched → stop. Print the per-slug file groups and ask the user to split the change into separate
/commitruns (one per plugin). Do not stage anything. - Single plugin slug + a few root-scope paths → ask the user via AskUserQuestion: "Bundle the root-scope files (
<list>) into the<slug>commit, or split them out as a separate root-scope commit?" Default to splitting if uncertain. - Root-scope only (no
plugins/<X>/...) → set$SCOPE = root,$PLUGIN_DIR = none. Continue.
The rest of this skill branches on $SCOPE.
1. Review the diff
Run git status and git diff HEAD (or git diff if nothing staged yet). Scan for:
- Secrets or credentials (
.env, API keys, tokens) - Large binaries or generated files that shouldn't be versioned
- Unrelated files that shouldn't be bundled in this 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.
- 11d ago First seen · 79 lines · 90 tokens per session scan A c5180b1e20e4
commit is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,283 once invoked, about $0.0004 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-10-02.
Other skills, from other repositories
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
implement-issue
Turn one labelled GitHub issue into one reviewed pull request, or stop with a stated reason. Use for every factory run; the message is a link to the issue.
git-master
Make atomic commits in the repo's own style, rebase or squash, and trace history with blame, bisect and pickaxe.
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.