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.
npx agentmods add commands/legacybridge-tech/claude-plugins/teds-checkpointgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWrote 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/legacybridge-tech/claude-plugins/teds-checkpoint)<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>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 | $0.00009 | $0.00611 |
| Opus 5 | $0.00005 | $0.00305 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
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.
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:
- Review recent work from
execution_log.md - Assess current progress
- Add checkpoint entry to
execution_log.md:### [HH:MM] - CHECKPOINT - Phase: [current phase] - Progress: [X%] - Summary: [accomplishments] - Next: [what remains] - Update
last_checkpointinstatus.yaml - 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.
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.
- 4d ago First seen · 106 lines · 9 tokens per session scan A e50d1a8a103a
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.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间,成员权限,团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.