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/drn/dots/amendnpx skills add drn/dots --skill amendgit clone --depth 1 https://github.com/drn/dotsWhat 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.00037 | $0.00569 |
| Opus 5 | $0.00018 | $0.00284 |
| Sonnet 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 2d 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.
- 2d 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 3d ago), licensed MIT. It adds 37 tokens to every session and 569 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.