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.
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.
curl -O https://raw.githubusercontent.com/dgunning/edgartools/main/.claude/commands/checkpoint.mdgit clone --depth 1 https://github.com/dgunning/edgartoolsWrote 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/commands/dgunning/edgartools/checkpoint)<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.
<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>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.00006 | $0.00763 |
| Opus 5.5 | $0.00002 | $0.00305 |
| Sonnet 5.5 | $0.00001 | $0.00153 |
| Haiku 4.5 | $0.00001 | $0.00076 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- checkpoint — 100% identical, 0 lines differ
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.
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.
- 2mo ago First seen · 121 lines · 6 tokens per session scan A 2e88f48a33e7
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.
checkpoint compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| checkpointdgunning/edgartools | Command | 2.8k | yesterday | MIT | A | 6 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |
| speckit.bug.fixgithub/spec-kit | Command | 148k | yesterday | MIT | A | 12 | Claude Code |