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/alex-ilgayev/mcpspy/git-commit-creatornpx skills add alex-ilgayev/MCPSpy --skill git-commit-creatorgit clone --depth 1 https://github.com/alex-ilgayev/MCPSpyWhat 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.00052 | $0.00350 |
| Opus 5 | $0.00026 | $0.00175 |
| Sonnet 5 | $0.00010 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
git-commit-creator 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 3d 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
Git Commit Creator Skill
Automates the creation of well-structured Git commits for the MCPSpy project.
Workflow
You should STRICTLY follow the following steps:
- Understand the commit status through
git status,git diffandgit diff --staged. - Analyze the scope and nature of changes
- Using
git checkout -b <branch-name>, create concise branch name with standard prefixes (e.g.,feat,chore,fix). - Using
git commit -m "<commit-message>", create a conventional commit message that accurately reflects the changes.
Commit Message Convention
- Use standard prefixes:
feat(component):,chore:,fix(component): - Component examples:
library-manager,ebpf,mcp,http,output - Brackets are optional but recommended for clarity
- Keep titles concise and descriptive
Examples
feat(library-manager): add support for container runtime detectionchore: update dependencies to latest versionsfix(ebpf): handle kernel version compatibility issues
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.
- 3d ago First seen · 39 lines · 52 tokens per session scan A 4d1ca6d492dd
git-commit-creator is a skill published in the GitHub repository alex-ilgayev/MCPSpy (517 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 350 once invoked, about $0.0003 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-30.
Other skills, from other repositories
implement-story
Implements a GitHub user story from planning through PR creation, with research, codebase analysis, and structured commits.
cis-aws-foundations-5.16
Ensure AWS Security Hub is enabled.
git-commit
Commit to Git safely: runs tests, security-reviews the diff, strips secrets and dead code, and enforces clean messages. Use before any commit or push.
ship
Automates the complete ship workflow for ccboard.
commit
Workflow Phase 11 — Commit Preparation and Execution. Stages and commits the work. Requires /grant-commit first (Git Commit Guard enforces a 15-min ad-hoc consent window; inside a workflow the grant is slug-scoped and one grant covers the whole landing).
commit-planner
Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never…