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 monkey1wizard/Golem-Agents-Legion --skill git-commitsgit clone --depth 1 https://github.com/monkey1wizard/Golem-Agents-LegionWrote 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/monkey1wizard/golem-agents-legion/git-commits)<a href="https://agentmods.dev/skills/monkey1wizard/golem-agents-legion/git-commits"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/git-commits/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/monkey1wizard/golem-agents-legion/git-commits"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/git-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 37 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 71 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00143 | $0.02412 |
| Opus 5.5 | $0.00057 | $0.00965 |
| Sonnet 5.5 | $0.00029 | $0.00482 |
| Haiku 4.5 | $0.00014 | $0.00241 |
Grade A, and why
git-commits 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commits Skill
Current State
!git diff --cached --stat !git log --oneline -5 !git status --short
Overview
Use gal commit-msg --context as the single front-end call: it does all necessary pre-work and returns up to five blocks — FILES (name-status), BASELINE (the deterministic type/scope), PLANS (per staged plan: slug, verb, title, Goal), PROMPTS (staged execution-prompt slugs), and CHANGES (hunk headers for non-plan code files). The Rust gal commit-msg command lives in crates/cli/src/gal/commit_msg.rs and replaces the retired Get-StagedCommitMessage.ps1 / get-staged-commit-message.sh helpers.
BASELINE is a path-and-status classifier: it gets the conventional-commit type and scope right (no-hijack — never inspects the diff body), but its subject is intentionally generic (e.g. refactor crates). Do not ship that generic subject verbatim — use PLANS's Goal (for staged plan files) or CHANGES's hunk headers (for code files) to write a subject that says what actually changed (e.g. rename gal-core crate to gal-engine), keeping the baseline's type(scope) prefix unless it is clearly wrong.
This repo's local rules override generic Conventional Commits guidance when they conflict. The final output must use a scoped header and stay in this repo's no-footer format unless the user explicitly asks for generic Conventional Commits instead.
Activation Rule
Treat all of the following as requests for this skill, even when the wording is casual, ungrammatical, abbreviated, or partially incorrect:
- "fallow the git-commits to give me commit msg"
- "git-commit"
- "git-commit-msg"
- "git commit message"
- "give me commit msg"
- "write commit msg"
- "summarize staged changes into commit message"
- "help me commit this"
If the user intent is clearly to produce commit-message wording from staged changes or a provided diff, activate this skill instead of asking a broad clarifying question.
Treat requests as commit intent when the user is asking to perform the commit, not merely draft wording. Examples: "git-commit", "commit this", "help me commit this", "use git-commits and commit", "generate the message and commit directly".
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 · 162 lines · 143 tokens per session scan A e8cddfef884f
git-commits is a skill published in the GitHub repository monkey1wizard/Golem-Agents-Legion (14 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 2,412 once invoked, about $0.0006 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-09-04.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.