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 dvasyliev/ai-dev-tools-getting-started --skill git-commitgit clone --depth 1 https://github.com/dvasyliev/ai-dev-tools-getting-startedWrote 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/dvasyliev/ai-dev-tools-getting-started/git-commit)<a href="https://agentmods.dev/skills/dvasyliev/ai-dev-tools-getting-started/git-commit"><img src="https://agentmods.dev/badge/skills/dvasyliev/ai-dev-tools-getting-started/git-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/dvasyliev/ai-dev-tools-getting-started/git-commit"><img src="https://agentmods.dev/badge/skills/dvasyliev/ai-dev-tools-getting-started/git-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.00087 | $0.00773 |
| Opus 5.5 | $0.00035 | $0.00309 |
| Sonnet 5.5 | $0.00017 | $0.00155 |
| Haiku 4.5 | $0.00009 | $0.00077 |
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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 127 lines · 87 tokens per session scan A 3c7728405943
git-commit is a skill published in the GitHub repository dvasyliev/ai-dev-tools-getting-started (21 stars, last pushed 6mo ago), with no licence file. It adds 87 tokens to every session and 773 once invoked, about $0.0003 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
pr-fallback
WHAT — When the repo has no GitHub PR template, structure the pull-request body using the default in references/pr-body-default.md. Pair with output-handshake and github-cli-workflow. Does not open the PR; HOW stays in the forge skill.
standup
Summarizes personal git activity by default, all authors' integrated changes with /standup all 24, and an opt-in merged-history audit with /standup all 24 audit. Reads diffs, links PR/review evidence, and separates merged from deployed. Use for an engineer standup, recap, or double-check of everything merged since a…
git-safety
Guards daily git work: blocks staged secrets, gates destructive git commands, installs pre-commit hooks, drives leak response. Use before commits, pushes, or history rewrites.
husky-test-coverage
Sets up or verifies Husky pre-commit hooks that enforce test coverage above 80% (configurable) for Node/TypeScript projects using Vitest (or Mocha with nyc/c8).
commit-summary
Writes Conventional Commit messages from git changes, splits unrelated changes, flags breaking changes, and commits after approval. Use when writing messages or committing work.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…