salesforce-claude-code: Skill for Claude Code

.cursor/skills/checkpoint/SKILL.md

checkpoint is a skill for Claude Code, Cursor from jiten-singh-shahi/salesforce-claude-code. It costs 28 tokens per session (372 once invoked), scanned A, original, MIT.

A progress-saving skill that creates named snapshots of your work with Git, a version-control tool.

In plain words
What is it for?
Use it to save, list, and restore work-in-progress checkpoints, including untracked files.
Why use it?
It gives you a recovery point before risky code changes, deployments, or Salesforce org changes.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: disable-model-invocation in frontmatter, but also installed under .cursor/.

This is jiten-singh-shahi/salesforce-claude-code's own configuration. It tells Claude Code and Cursor how to work on salesforce-claude-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything salesforce-claude-code configures →

Part of the salesforce-claude-code plugin — 41 skills, 17 agents shipped together

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jiten-singh-shahi/salesforce-claude-code/main/.cursor/skills/checkpoint/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-code

Made for: Claude Code, Cursor.

Or install salesforce-claude-code, the plugin that ships this one along with the rest of its 41 skills, 17 agents.

Wrote 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.

agentmods badge for checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/skills/jiten-singh-shahi/salesforce-claude-code/checkpoint.svg)](https://agentmods.dev/skills/jiten-singh-shahi/salesforce-claude-code/checkpoint)
Your own site
<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>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 372 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 5b23fd3dd4f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

.cursor/skills/checkpoint/SKILL.md · 51 lines

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

  1. Create checkpointgit stash push --include-untracked -m "checkpoint: <name> [<timestamp>]"
  2. Log metadata — Append to .claude/checkpoints.log:
    • Timestamp
    • Checkpoint name
    • Files changed (count)
    • Current branch
  3. Verify — Confirm working tree is clean after stash

Operations

  • checkpoint save <name> — Create new checkpoint
  • checkpoint list — Show all checkpoints from log
  • checkpoint restore <name> — Apply the named stash (git stash apply; keeps the stash entry safe). Find the stash reference via git stash list | grep "<name>", then git stash apply stash@{N}. After verifying the restore, drop with git 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
Changes

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.

  1. 8d ago First seen · 51 lines · 28 tokens per session scan A 5b23fd3dd4f2

Subscribe to this mod's changes

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.

Related

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…

cwinvestments/memstack · 92 tokens

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.

cwinvestments/memstack · 62 tokens

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.

travisjneuman/.claude · 53 tokens

validate-changes

Evaluate staged changes using LLM-as-a-Judge before committing.

FlorianBruniaux/claude-code-ultimate-guide · 16 tokens

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…

damusix/atomic-claude · 106 tokens

commit

Generate a conventional commit message for staged changes.

FlorianBruniaux/claude-code-ultimate-guide · 10 tokens