Borrowing it
Nothing to install: this file belongs to jiten-singh-shahi/salesforce-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jiten-singh-shahi/salesforce-claude-code/main/.cursor/skills/checkpoint/SKILL.mdgit clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-codeWrote 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/jiten-singh-shahi/salesforce-claude-code/checkpoint)<a href="https://agentmods.dev/skills/jiten-singh-shahi/salesforce-claude-code/checkpoint"><img src="https://agentmods.dev/badge/skills/jiten-singh-shahi/salesforce-claude-code/checkpoint.svg" alt="Measured on agentmods" 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.00028 | $0.00372 |
| Opus 5 | $0.00014 | $0.00186 |
| Sonnet 5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
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 8d 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.
What it actually says
Checkpoint — Named Progress Snapshots
Save current progress as a named checkpoint for easy recovery.
When to Use
- When you want to save work-in-progress before attempting a risky change
- When starting a refactoring pass and need a safe rollback point
- When switching between tasks and want to preserve current state
- When you need to snapshot progress at key milestones during a long session
- When collaborating and want to share a recoverable state with another agent or session
Usage
checkpoint [name]
Workflow
- Create checkpoint —
git stash push --include-untracked -m "checkpoint: <name> [<timestamp>]" - Log metadata — Append to
.claude/checkpoints.log:- Timestamp
- Checkpoint name
- Files changed (count)
- Current branch
- Verify — Confirm working tree is clean after stash
Operations
checkpoint save <name>— Create new checkpointcheckpoint list— Show all checkpoints from logcheckpoint restore <name>— Apply the named stash (git stash apply; keeps the stash entry safe). Find the stash reference viagit stash list | grep "<name>", thengit stash apply stash@{N}. After verifying the restore, drop withgit stash drop stash@{N}.checkpoint verify— Verify current state matches last checkpoint
Examples
checkpoint save before-trigger-refactor
checkpoint list
checkpoint restore before-trigger-refactor
checkpoint verify
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.
- 8d ago First seen · 51 lines · 28 tokens per session scan A 5b23fd3dd4f2
checkpoint is a skill published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (16 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 372 once invoked, about $0.0001 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
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
memstack-security-secrets-scanner
Use this skill when the user says 'scan for secrets', 'check for leaked keys', 'secrets scanner', 'hardcoded credentials', 'API key leak', or needs to detect exposed secrets in source code. Do NOT use for dependency vulnerabilities or RLS auditing.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…
commit
Generate a conventional commit message for staged changes.