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/signnow/sn-mcp-server/git-commitnpx skills add signnow/sn-mcp-server --skill git-commitgit clone --depth 1 https://github.com/signnow/sn-mcp-serverWhat 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.00020 | $0.00941 |
| Opus 5 | $0.00010 | $0.00470 |
| Sonnet 5 | $0.00004 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
git-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 yesterday.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit & Commit Message (SignNow MCP Server)
Critical rules
- NEVER commit directly to
mainormaster. Always work on a dedicated branch. - Do not commit unless all required checks pass (see below).
- Keep each commit one logical change (single change type).
- Commit message follows Conventional Commits.
Workflow
- Create (or switch to) a feature branch — MANDATORY
- NEVER commit to
mainormasterdirectly. - If not already on a feature branch, create one:
git checkout -b <type>/<short-description>(e.g.,feat/add-embedded-editor,fix/token-refresh)
- Branch naming:
<type>/<short-description>using the same type vocabulary as commit types.
- Check what changed
git status -sb- If changes are mixed, split into separate commits using
git add -p.
- Review staged diff
- Stage what belongs to this commit.
- Inspect:
git diff --cached
- Run required checks (must be green)
pytest tests/unit/ -v
ruff check src/ tests/
ruff format --check src/ tests/
- If any command fails, fix the issue and rerun all checks.
- Compose the commit message
Subject format
<type>(<scope>)?: <subject>
Subject rules
- Imperative mood ("Add", "Fix", "Remove", "Prevent", ...)
- No trailing period
- Prefer ≤ 72 chars
Body (optional)
- Explain why, not just what.
- Wrap lines at ~80 chars.
Breaking changes (if applicable)
-
Add
!after type/scope:feat!: ...orfeat(tools)!: ... -
Add footer:
BREAKING CHANGE: <what breaks and migration notes>
- Commit
-
One-liner (no body/footer needed):
git commit -m "..."
-
Otherwise:
git commitand write subject + body in editor.
- Post-commit sanity
git show --stat- Ensure no accidental files were committed.
- Push
git push
- Create Pull Request (if none exists)
- After pushing, check whether a PR already exists for the current branch:
- Use the GitHub MCP tool (
search_pull_requests) to check.
- Use the GitHub MCP tool (
- If no PR exists → create one immediately.
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.
- yesterday First seen · 134 lines · 20 tokens per session scan A 3b815676d8e0
git-commit is a skill published in the GitHub repository signnow/sn-mcp-server (8 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 941 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
webhook-handler-patterns
Best practices for webhook handlers: verify → parse → handle idempotently. Covers idempotency, error handling, retry logic, framework-specific gotchas (Express, Next.js, FastAPI). Use when implementing any webhook receiver.
api
FastAPI + async/sync HTTP client patterns, JWT auth, multi-provider routing, Pydantic request/response models, CORS, background tasks, and typed frontend API clients — synthesized from lead-gen-engine and seo-geo-aeo-engine.
webfetch
Fetch live web pages, inspect responses, extract relevant content, and summarize findings with links.
free-business-template-library
Finds relevant PandaDoc business document templates in a catalog of 1,000+ free templates and returns direct links for customization and eSignature. Use when the user asks for a ready-made business document template or wants to find, browse, compare, or select PandaDoc templates for proposals, contracts, agreements…
datamodel-code-generator
Use this skill when the user wants Python data models, Pydantic models, dataclasses, TypedDicts, msgspec structs, or type-safe Python classes generated from OpenAPI, AsyncAPI, JSON Schema, GraphQL, JSON/YAML/CSV sample data, MCP tool schemas, Protocol Buffers, XML Schema, Apache Avro, or existing Python model objects.…
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.