teds-checkpoint

teds-checkpoint is a command for coding agents from legacybridge-tech/claude-plugins. It costs 9 tokens per session (611 once invoked), scanned A, original, MIT.

A TEDS command that saves a checkpoint for an active task. TEDS is a system for documenting coding work so it can be resumed later.

In plain words
What is it for?
Use it before stopping work or after a major milestone to update the task log and its last-checkpoint status.
Why use it?
It creates a recorded pause point showing what has been done, how far the task has progressed, and what remains.

Command

Part of the teds-plugin plugin — 6 commands, 5 agents shipped together

Install

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.

agentmods
npx agentmods add commands/legacybridge-tech/claude-plugins/teds-checkpoint
Clone the repo
git clone --depth 1 https://github.com/legacybridge-tech/claude-plugins

Or install teds-plugin, the plugin that ships this one along with the rest of its 6 commands, 5 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 teds-checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/commands/legacybridge-tech/claude-plugins/teds-checkpoint.svg)](https://agentmods.dev/commands/legacybridge-tech/claude-plugins/teds-checkpoint)
Your own site
<a href="https://agentmods.dev/commands/legacybridge-tech/claude-plugins/teds-checkpoint"><img src="https://agentmods.dev/badge/commands/legacybridge-tech/claude-plugins/teds-checkpoint.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00009 $0.00611
Opus 5 $0.00005 $0.00305
Sonnet 5 $0.00002 $0.00122
Haiku 4.5 $0.00001 $0.00061

Measured 4d ago against content hash e50d1a8a103a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

teds-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 4d 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.

teds/commands/teds-checkpoint.md · 106 lines

How it starts

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

Create TEDS Checkpoint

Create an immediate checkpoint in the currently active TEDS task.

Usage

/teds-checkpoint [optional-task-id]

Examples

# Create checkpoint in current task context
/teds-checkpoint

# Create checkpoint for specific task
/teds-checkpoint 20250116-1430-refactor-auth

What is a Checkpoint?

A checkpoint is a safe pause point that captures:

  • Current phase and progress percentage
  • Summary of what has been accomplished
  • What remains to be done
  • Timestamp for recovery reference

Think of it as a "save game" point—you can safely stop work and resume from here later.

What This Does

The agent will:

  1. Review recent work from execution_log.md
  2. Assess current progress
  3. Add checkpoint entry to execution_log.md:
    ### [HH:MM] - CHECKPOINT
    - Phase: [current phase]
    - Progress: [X%]
    - Summary: [accomplishments]
    - Next: [what remains]
    
  4. Update last_checkpoint in status.yaml
  5. Confirm: "Checkpoint created. Safe to pause here."

Automatic Checkpoints

The executor agent automatically creates checkpoints:

  • Every 30+ minutes of active work
  • At completion of major milestones
  • When transitioning between phases

Manual checkpoints are useful when:

  • You want to pause before the automatic interval
  • You've reached a logical stopping point
  • You're about to try something risky
  • You're switching focus to another task

Checkpoint Best Practices

Good times to checkpoint:

  • ✅ Just completed a significant feature
  • ✅ About to refactor or make large changes
  • ✅ End of work session
  • ✅ Before switching context

Don't checkpoint:

  • ❌ In the middle of an incomplete action
  • ❌ When build/tests are failing
  • ❌ When blocked and unsure how to proceed (mark as blocked instead)

Viewing Checkpoints

To see all checkpoints in a task:

# View full execution log
cat workspace/active_tasks/[task-id]/execution_log.md | grep "CHECKPOINT"

Or use:

/teds-status [task-id]

This shows the last checkpoint time.

Read the full file on GitHub · 106 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. 4d ago First seen · 106 lines · 9 tokens per session scan A e50d1a8a103a

Subscribe to this mod's changes

teds-checkpoint is a command published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 611 once invoked, about $0.0000 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-31.