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/denysdovhan/agents/commitnpx skills add denysdovhan/agents --skill commitgit clone --depth 1 https://github.com/denysdovhan/agentsWhat 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.00035 | $0.00614 |
| Opus 5 | $0.00017 | $0.00307 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Skill
Use this skill when the work is already implemented and the next step is to create a clean git commit.
Goals
- Keep the commit scoped to the intended change
- Write a concise, descriptive commit message
- Avoid including unrelated modified files
Workflow
- Inspect the working tree before committing.
- Confirm which files belong to the requested change.
- Detect the repository's commit-message rules and style.
- Stage only the relevant files.
- Write a commit message that follows the detected style and summarizes the user-visible change.
- Create the commit without rewriting unrelated history.
Commit Message Style
Before writing the message, check for explicit rules in repository instructions
such as AGENTS.md, CONTRIBUTING.md, README.md, pull request templates,
package scripts, or commitlint configuration. Explicit project or user rules
override history.
If no explicit rule exists, inspect recent commits:
git log --format=%s -n 20
git log --format=%B -n 5
Use the dominant style from relevant recent history:
- Conventional commits: use
type(scope): subjectortype: subjectwhen recent history uses prefixes such asfeat:,fix:,docs:,chore:,ci:,refactor:, or scoped variants. - Simple subjects: use a concise imperative subject such as
Update skill validation workflowwhen history uses plain sentence-style commit subjects. - Multiline commits: include a blank line and body when recent non-merge commits commonly include bodies, when the change needs context, or when the user asks for references/explanations. Keep the subject aligned with the detected subject style.
- Mixed history: prefer the style used by recent commits touching the same area. Do not imitate merge commits.
Guidelines
- Respect what the user already staged: inspect
git diff --cachedbefore staging anything, treat pre-staged content as intentional, and do not unstage it unless it clearly does not belong to the requested change — call that out instead. - If a pre-commit hook fails, fix the reported problem and retry the commit. If a hook rewrites files, restage only the hook-modified files and commit again. Do not bypass hooks with
--no-verifyunless the user explicitly asks. - Do not stage unrelated files just to make the tree clean.
- Prefer one focused commit over a mixed commit.
- Use imperative subjects unless the repository's explicit rules or dominant history use another style.
- If the tree contains unexpected changes, call them out before committing.
- Do not amend existing commits unless explicitly requested.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 65 lines · 35 tokens per session scan A 25b43615f6e5
commit is a skill published in the GitHub repository denysdovhan/agents (17 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 614 once invoked, about $0.0002 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
abbreviated-git-status
How autonomous coding agents use short-format and porcelain git status flags to eliminate 85% of shell output token overhead while preserving exact branch and staging state.
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
aria
Designs the data model, API contracts, and structural foundation of the system.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.