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/ggemba/squad-mcp/commit-suggestnpx skills add ggemba/squad-mcp --skill commit-suggestgit clone --depth 1 https://github.com/ggemba/squad-mcpWhat 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 | $0.00120 | $0.03357 |
| Opus 5 | $0.00060 | $0.01679 |
| Sonnet 5 | $0.00024 | $0.00671 |
| Haiku 4.5 | $0.00012 | $0.00336 |
Grade A, and why
commit-suggest 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 2d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Commit Suggest
Objective
Generate a short, accurate Conventional Commits message for the current changes. Suggestion only — the user copies and runs git commit themselves.
Inviolable Rules
-
Read-only — allowlist of git commands. The ONLY git commands this skill may run are:
git status(any flags read-only)git diff— without--output=/-O(those write to disk)git log— without--output=/-Ogit rev-parsegit config --get <key>— only the--get <key>form. Any othergit configinvocation (--add,--unset,--global,--list,--edit,-e,--rename-section,--remove-section, etc.) is forbidden.git ls-filesgit show <ref>:<path>— only the<ref>:<path>pinned-blob form. Forbid all flag forms:--textconv,--ext-diff,--output=,-O,--format=, etc., because filters and writers are unsafe.
Any other git invocation, with any flags, is forbidden — including commands not enumerated here. If uncertain whether a command mutates state, do not run it. Do NOT use
-c <key>=<value>config overrides,--exec-path,--git-dir,--work-tree, or--namespaceglobal flags — they bypass per-command intent.Specifically forbidden examples (non-exhaustive):
git commit,git add,git push,git pull,git fetch,git rm,git restore,git reset,git checkout,git switch,git stash,git merge,git rebase,git tag,git branch,git cherry-pick,git revert,git worktree,git clean,git apply(any form, including--check),git am,git mv,git notes,git replace,git update-ref,git remote,git submodule,git filter-branch,git filter-repo,git gc,git reflog,git fsck --full,git bisect,git format-patch -o,git rerere,git prune,git repack,git sparse-checkout,git hooks. -
No AI attribution. Never add
Co-Authored-By: Claude,Co-Authored-By: Anthropic,Co-Authored-By: AI,Generated with,Made by AI,<[email protected]>, or any equivalent trailer/line that attributes authorship to a model. The author is always the user. This applies to subject, body, and footer. -
No file edits. Never edit any file as part of this skill. Output is text only.
-
Suggestion, not execution. Always end with a reminder that the user runs the commit themselves.
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.
- 2d ago First seen · 258 lines · 0 tokens per session scan A 44993de80277
commit-suggest is a skill published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 120 tokens to every session and 3,357 once invoked, about $0.0006 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
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
commit
Analyze changes, write a conventional commit, and (when shipping) open a PR with closing keywords so referenced issues auto-close on merge. Use when the user asks to commit, push, or open a PR.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
commit_push
Format code, review changes, commit, and push to remote.
contribution-guidelines
Contribution process with PR workflow, code review standards, commit conventions, and open source best practices.