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/codewithmukesh/dotnet-claude-kit/checkpointnpx skills add codewithmukesh/dotnet-claude-kit --skill checkpointgit clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kitWhat 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.00096 | $0.00812 |
| Opus 5 | $0.00048 | $0.00406 |
| Sonnet 5 | $0.00019 | $0.00162 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
checkpoint 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 3d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/checkpoint
What
A quick mid-session save that banks the known-good state in two moves:
- Descriptive git commit — stage relevant changes and commit with a message that summarizes the work.
- Brief handoff note — write
.claude/handoff.mdso a resumed session (or you, after a botched refactor) knows exactly where things stand.
Checkpoint is the mid-session save; /wrap-up is the end-of-session ritual.
Checkpoint commits and jots a note, then keeps working. Wrap-up does the full
handoff plus learning extraction into MEMORY.md.
When
- Before a risky refactor or destructive change — checkpoint the known-good state
- When switching to a different task or feature mid-session
- After completing a logical unit of work — bank it
- User says "checkpoint", "save progress", "save state", "pause here"
- If the session is actually ending, use
/wrap-upfor the full ritual
How
- Assess state —
git statusandgit diffto see staged and unstaged changes. - Stage changes — Stage specific files; never
git add -A. Exclude generated files, build artifacts, and secrets (.env, credentials). - Commit — Descriptive message following the repo's commit style
(conventional prefixes:
feat:,fix:,refactor:). New commit, never amend. If there is nothing to commit, skip to the handoff. - Write handoff note —
.claude/handoff.md, same format as/wrap-upbut abbreviated: Completed, Pending (with specific next steps), Learned (only if something non-obvious surfaced), and Context (branch + commit hash). One file, always overwritten. - Confirm — Report the commit hash and the handoff summary, then resume work.
Safety Rules
- Never push, force-push, or touch remote branches
- Never commit secrets
- Never amend — a checkpoint is a new commit you can return to
- No changes to commit? Update the handoff only
Example
User: /checkpoint — about to try the EF Core split-query refactor
Claude: 3 files modified, 1 new.
Commit a1b2c3d: "feat: add CreateOrder validation with FluentValidation"
- src/Orders/Features/CreateOrder.cs
- src/Orders/Features/CreateOrderValidator.cs (new)
- tests/Orders.Tests/Features/CreateOrderTests.cs
Handoff updated (.claude/handoff.md):
## Completed
- [x] CreateOrder validation + 3 test scenarios
## Pending
- [ ] Split-query refactor in GetOrderDetails (about to attempt)
## Context
- Branch: feature/order-validation | Checkpoint: a1b2c3d
Checkpoint saved — safe to proceed with the risky refactor.
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.
- 3d ago First seen · 87 lines · 96 tokens per session scan A c0d87efe95d6
checkpoint is a skill published in the GitHub repository codewithmukesh/dotnet-claude-kit (689 stars, last pushed 26d ago), licensed MIT. It adds 96 tokens to every session and 812 once invoked, about $0.0005 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
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…