edgartools: Command for Claude Code

.claude/commands/checkpoint.md

checkpoint is a command for Claude Code from dgunning/edgartools. It costs 6 tokens per session (763 once invoked), scanned A, original, MIT.

A command that writes a progress checkpoint describing the current coding session so work can continue after the conversation is restarted.

In plain words
What is it for?
Use it before a context reset or when handing ongoing work to a later session.
Why use it?
It preserves decisions, completed work, open tasks, important files, and blockers when the current context needs to be cleared.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is dgunning/edgartools's own configuration. It tells Claude Code how to work on edgartools 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 edgartools configures →

About the project

EdgarTools is a Python library that turns SEC EDGAR filings into structured, typed data, including financial statements, insider trades, fund holdings, and other filing types. It is used to analyze regulatory filings in notebooks, data pipelines, and AI systems. Its catalogue add-ons operate the library through skills, commands, instructions, and an MCP server.

dgunning/edgartools · 2,837 stars · on GitHub · edgartools.readthedocs.io

Reuse

Borrowing it

Nothing to install: this file belongs to dgunning/edgartools. 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/dgunning/edgartools/main/.claude/commands/checkpoint.md
Clone the repo
git clone --depth 1 https://github.com/dgunning/edgartools

Made for: Claude Code.

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/commands/dgunning/edgartools/checkpoint/github.svg)](https://agentmods.dev/commands/dgunning/edgartools/checkpoint)
Your own site
<a href="https://agentmods.dev/commands/dgunning/edgartools/checkpoint"><img src="https://agentmods.dev/badge/commands/dgunning/edgartools/checkpoint/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.

agentmods 80×15 button for checkpoint

Your own site · 80×15
<a href="https://agentmods.dev/commands/dgunning/edgartools/checkpoint"><img src="https://agentmods.dev/badge/commands/dgunning/edgartools/checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 763 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.00006 $0.00763
Opus 5.5 $0.00002 $0.00305
Sonnet 5.5 $0.00001 $0.00153
Haiku 4.5 $0.00001 $0.00076

Measured 2mo ago against content hash 2e88f48a33e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/checkpoint.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Progress Checkpoint

You are creating a checkpoint of the current work session to enable a clean context restart.

Step 1: Determine Context

Ask yourself:

  • What is the main task we're working on?
  • What's a brief, descriptive name for this task? (e.g., "oauth-migration", "fix-bug-429", "add-13f-support")

Step 2: Create Checkpoint Document

Create a progress document with this structure:

Filename: docs-internal/sessions/session-{task-name}-{YYYY-MM-DD}.md

Use today's date and a brief task name (kebab-case, max 3-4 words).

Document Structure:

# Session Checkpoint: {Task Name}

**Date**: {YYYY-MM-DD}
**Time**: {HH:MM}
**Branch**: {current git branch}

## Task Summary
{1-2 sentence description of what we're working on}

## Completed ✅

- {Specific accomplishment with file path}
- {Another completed item}

## In Progress 🔄

- {Current work item}
- {Any blockers or issues encountered}

## Remaining Tasks ⬜

- [ ] {Next task to complete}
- [ ] {Another remaining task}

## Key Decisions 🎯

- **{Decision topic}**: {What was decided and why}
- **{Another decision}**: {Rationale}

## Important Files 📁

- `path/to/file.py` - {What this file does in this context}
- `path/to/another.py` - {Why this file matters}

## Next Steps 🚀

1. {Explicit next action}
2. {Second action}
3. {Third action}

## Context Notes

{Any important context that would be lost after /clear - patterns discovered,
gotchas encountered, areas of concern, etc.}

Step 3: Quality Check

Ensure the checkpoint includes:

  • ✅ Specific file paths (not vague "updated files")
  • ✅ Clear next steps (actionable, not vague)
  • ✅ Technical decisions with rationale
  • ✅ Any blockers or issues that need attention
  • ✅ Brief enough to scan quickly (<150 lines ideal)

Step 4: Save and Instruct

After creating the document, tell the user:

✅ Checkpoint saved to: {filename}

To continue after clearing context:
1. Type: /clear
2. Type: @{filename} /catchup
3. Say: "Continue with {specific next step from Next Steps}"

Alternative quick restart:
- /catchup (will catch git changes including this checkpoint if committed)

Ready to clear when you are.

Read the full file on GitHub · 121 lines

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. 2mo ago First seen · 121 lines · 6 tokens per session scan A 2e88f48a33e7

Subscribe to this mod's changes

checkpoint is a command published in the GitHub repository dgunning/edgartools (2,837 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 763 once invoked, about $0.0000 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.

Related

checkpoint compared with commands from other repositories

checkpoint next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
checkpointdgunning/edgartoolsCommand2.8kyesterdayMITA6Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code
speckit.bug.fixgithub/spec-kitCommand148kyesterdayMITA12Claude Code