agentmods.dev

pod-checkpoint

pod-checkpoint is a skill for Claude Code from Snowflake-Labs/cocoplus. It costs 36 tokens per session (1,382 once invoked), scanned A, original, MIT.

A checkpoint tool that writes a structured recovery snapshot of the current project state before the agent's context is reset.

In plain words
What is it for?
Use it to record recovery information in the project's lifecycle checkpoint file before switching context.
Why use it?
It preserves important progress and decisions so work can resume without reconstructing the whole task.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

not rated 726repo +3 changed 21d ago A scan 36 tokens original MIT

Good fit Use it to record recovery information in the project's lifecycle checkpoint file before switching context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/snowflake-labs/cocoplus/pod-checkpoint
View source ↗ Snowflake-Labs/cocoplus cocoplus.dev
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.

Any agent
npx skills add Snowflake-Labs/cocoplus --skill pod-checkpoint
Clone the repo
git clone --depth 1 https://github.com/Snowflake-Labs/cocoplus

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 pod-checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-checkpoint/github.svg)](https://agentmods.dev/skills/snowflake-labs/cocoplus/pod-checkpoint)
Your own site
<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/pod-checkpoint"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-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 pod-checkpoint

Your own site · 80×15
<a href="https://agentmods.dev/skills/snowflake-labs/cocoplus/pod-checkpoint"><img src="https://agentmods.dev/badge/skills/snowflake-labs/cocoplus/pod-checkpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,382 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.00036 $0.01382
Opus 5.5 $0.00014 $0.00553
Sonnet 5.5 $0.00007 $0.00276
Haiku 4.5 $0.00004 $0.00138

Measured 21d ago against content hash c06ff55940d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pod-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 21d 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.

.cortex/skills/cocopod/pod-checkpoint/SKILL.md · 142 lines

How it starts

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

$pod checkpoint

Write a structured recovery snapshot to .cocoplus/lifecycle/checkpoint.md. Use this before $clear to ensure $pod resume can restore your exact position.

Preconditions

  • .cocoplus/ directory must exist (run $pod init first)
  • No arguments accepted

Step-by-Step Behavior

  1. Verify initialization: Check .cocoplus/ exists. If not, output: "CocoPlus not initialized. Run $pod init first." and exit.

  2. Read current lifecycle phase: Read .cocoplus/lifecycle/meta.json. Extract: current phase, phase ID, completion timestamps.

  3. Read in-progress flow stage: Read .cocoplus/flow.json. Find the stage with status: "running" or the next status: "pending" stage. Extract: stage ID, stage name, checkpoint validation status.

  4. Read last 5 decisions: Read .cocoplus/memory/decisions.md. Extract the 5 most recent entries (newest first) — capture ID, brief description, date.

  5. Read open must-fix items: Read .cocoplus/lifecycle/review.md if it exists. Extract any must-fix findings that have not been resolved.

  6. Read active HITL stages: Read .cocoplus/flow.json. Find all stages with "hitl": true and status: "pending" awaiting developer approval.

  7. Read triggered seeds: Scan .cocoplus/seeds/*.yaml for entries with status: triggered.

  8. Read CocoHarvest status: Read .cocoplus/harvest/ directory for any *-tasks.json files with in-progress stages. Extract harvest ID and agent summary.

  9. Assess context utilization: Read .cocoplus/meter/current-session.json if it exists. Approximate utilization from token accumulation. If context utilization data is unavailable, omit this field gracefully.

  10. Write checkpoint file: Write all gathered state to .cocoplus/lifecycle/checkpoint.md (overwrite if it exists):

---
checkpoint_date: [ISO8601]
lifecycle_phase: [phase name]
phase_id: [phase-id or null]
context_utilization: [percentage or "unavailable"]
---

# CocoPlus Checkpoint — [ISO8601]

## Lifecycle State
- **Phase:** [current phase] (ID: [phase-id])
- **Last completed:** [last phase completed with timestamp]

## In-Progress Flow Stage
- **Stage:** [stage-id] — [stage name]
- **Persona:** [assigned persona]
- **Checkpoints validated:** [N / total]
- **Status:** [running / pending]

## Last 5 Decisions
1. [[decision-id]] [brief description] — [date]
2. ...

## Pending Must-Fix Items
[List from review.md, or "None"]

## HITL Stages Awaiting Approval
[List of hitl: true stages with pending status, or "None"]

## Active CocoHarvest Run
- **Harvest ID:** [run-id or "None active"]
- **Agents:** [summary of in-progress agents]

## Triggered Seeds Ready for Promotion
[List of triggered seeds, or "None"]

Read the full file on GitHub · 142 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. 21d ago Changed · +112 lines · +17 tokens per session c06ff55940d0
  2. 1mo ago First seen · 30 lines · 19 tokens per session scan A 87742a16ace8

Subscribe to this mod's changes

pod-checkpoint is a skill published in the GitHub repository Snowflake-Labs/cocoplus (726 stars, last pushed 21d ago), licensed MIT. It adds 36 tokens to every session and 1,382 once invoked, about $0.0001 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-09-03.

Building agentsLLMMemory and contextagentsagentskillscocopluscortexcortexaisnowflake
Related

Other skills, from other repositories

knowledge_store_skill

Skill for working with local .knowledge.yaml files via KnowledgeStore. Use this when you need to recall, search, or manage directory-local memories and knowledge links stored in plain YAML alongside the user's project files. KnowledgeStore is directory-scoped. Each directory that contains a .knowledge.yaml file…

NPC-Worldwide/npcpy · 346 tokens

remember

Write-side memory: stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Use when something worth persisting across sessions was just learned or decided. To search or read existing memory, invoke memory; to debug retrieval internals…

yonatangross/orchestkit · 66 tokens

memory

Read-side memory operations on the knowledge graph: search past decisions and patterns, load session context, view decision timelines, render Mermaid graph visualizations. Subcommands: search, load, history, viz, status. Use when finding or reviewing what memory already holds. For storing new knowledge instead, invoke…

yonatangross/orchestkit · 77 tokens

llm-wiki

Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…

sammcj/agentic-coding · 82 tokens

authoring-claude-md

Creating and maintaining CLAUDE.md project memory files and .claude/rules/ rule files that provide non-obvious codebase context. Use when (1) creating a new CLAUDE.md for a project, (2) adding architectural patterns or design decisions to existing CLAUDE.md, (3) capturing project-specific conventions that aren't…

sammcj/agentic-coding · 93 tokens

sixb-memory

Organize the memory into topic files, and merge a save that conflicts.

sixb-ai/sixb · 19 tokens