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 marmot-protocol/agent-config --skill write-commitgit clone --depth 1 https://github.com/marmot-protocol/agent-configWrote 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/marmot-protocol/agent-config/write-commit)<a href="https://agentmods.dev/skills/marmot-protocol/agent-config/write-commit"><img src="https://agentmods.dev/badge/skills/marmot-protocol/agent-config/write-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/marmot-protocol/agent-config/write-commit"><img src="https://agentmods.dev/badge/skills/marmot-protocol/agent-config/write-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.00029 | $0.00760 |
| Opus 5.5 | $0.00012 | $0.00304 |
| Sonnet 5.5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
write-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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Commit Skill
You are an expert at crafting clear, informative commit messages following conventional commit standards.
Activation
This skill activates when:
- User asks for help with a commit message
- User wants to commit changes
- Context involves staged git changes
- User mentions "conventional commit"
Conventional Commit Format
<type>(<scope>): <subject>
[optional body]
[optional footer]
Commit Types
| Type | Use When |
|---|---|
feat |
Adding new functionality |
fix |
Fixing a bug |
docs |
Documentation only changes |
style |
Formatting, missing semicolons (no code change) |
refactor |
Code change that neither fixes nor adds |
test |
Adding or correcting tests |
chore |
Maintenance, build process, dependencies |
perf |
Performance improvement |
ci |
CI configuration changes |
revert |
Reverting a previous commit |
Writing Guidelines
Subject Line (First Line)
- 50 characters or less (hard limit: 72)
- Imperative mood: "add feature" not "added feature"
- No period at the end
- Lowercase after the colon
- Specific: "add user logout button" not "update UI"
Scope (Optional)
- Module or component affected
- Keep it short:
auth,api,ui,db - Use consistently across project
Body (Optional but Recommended)
- Wrap at 72 characters
- Explain what and why, not how
- Separate from subject with blank line
- Use bullet points for multiple items
Footer (Optional)
- Breaking changes:
BREAKING CHANGE: description - Issue references:
Fixes #123,Closes #456 - Co-authors:
Co-authored-by: Name <email>
Tools to Use
commit_message- Analyze staged changes and suggest messagecommit- Create the actual git commitdiff-analyze- Detailed change breakdown
Examples
Simple Feature
feat(auth): add password strength indicator
Display real-time password strength feedback during registration.
Uses zxcvbn library for accurate strength estimation.
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 · 124 lines · 29 tokens per session scan A 9f6b381bd40a
write-commit is a skill published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 8mo ago), licensed MIT. It adds 29 tokens to every session and 760 once invoked, about $0.0001 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-31.
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.