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 drn/dots --skill amendgit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/amend)<a href="https://agentmods.dev/skills/drn/dots/amend"><img src="https://agentmods.dev/badge/skills/drn/dots/amend/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/drn/dots/amend"><img src="https://agentmods.dev/badge/skills/drn/dots/amend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00569 |
| Opus 5.5 | $0.00015 | $0.00228 |
| Sonnet 5.5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
amend 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amend Last Commit
Rewrite the last commit message with a clear, descriptive summary based on the actual changes.
Arguments
$ARGUMENTS- Optional: specific instructions for the commit message (e.g., "mention the performance improvement")
Context
- Current branch: !
git branch --show-current - Last commit: !
git log -1 --format="%H %s" 2>/dev/null | head -1 - Last commit body: !
git log -1 --format="%b" 2>/dev/null | head -20 - Diff stat: !
git diff HEAD~1 --stat 2>/dev/null | head -30
Instructions
Step 1: Understand the changes
- Read the diff of the last commit:
git diff HEAD~1(full diff, not just stat) - Read any files that were added or significantly changed to understand their purpose
- Check the current commit message — if it's already descriptive and accurate, tell the user and stop
Step 2: Draft the message
Write a commit message following this structure:
Subject line (first line):
- Imperative mood ("Add", "Fix", "Update", not "Added", "Fixes")
- Under 72 characters
- Summarize WHAT changed and WHY at a high level
- No trailing period
Body (separated by blank line, optional but preferred for non-trivial changes):
- Explain what the change does and why it was made
- Wrap lines at 72 characters
- Focus on context that isn't obvious from the diff
- Skip the body for truly trivial changes (typo fixes, version bumps)
Step 3: Amend the commit
Run git commit --amend with the new message. Use a HEREDOC to pass the message:
git commit --amend -m "$(cat <<'EOF'
Subject line here
Body paragraph here explaining the change in more detail.
EOF
)"
Step 4: Confirm
Show the user the new commit with git log -1 so they can verify.
Rules
- Never change the commit contents — only the message. Do not stage or unstage files.
- Preserve co-author trailers from the original message if present.
- If the working tree has staged changes, warn the user that
--amendwill include them, and ask before proceeding. - If
$ARGUMENTScontains specific instructions, incorporate them into the message.
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 · 68 lines · 37 tokens per session scan A 49d75689475d
amend is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 37 tokens to every session and 569 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-30.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.