What is persisting-progress-across-sessions?

A progress-saving guide for resuming an interrupted multi-step coding task across sessions. It uses a MANIFEST.yaml file to record completed phases, active work, agent results, and validation status.

Use it to resume orchestration runs, inspect earlier phase outputs, and continue implementation or review from the recorded state.

It prevents completed work from being repeated after a session ends, crashes, or runs out of context. It also shows which phase should continue next.

persisting-progress-across-sessions — Skill for Claude Code and Codex

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 porcupine-md/jonggrang --skill persisting-progress-across-sessions

Clone the repo

git clone --depth 1 https://github.com/porcupine-md/jonggrang

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/porcupine-md/jonggrang/persisting-progress-across-sessions/github.svg)](https://agentmods.dev/skills/porcupine-md/jonggrang/persisting-progress-across-sessions)

Your own site

<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/persisting-progress-across-sessions"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/persisting-progress-across-sessions/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/persisting-progress-across-sessions"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/persisting-progress-across-sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 865 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00022	$0.00865
Opus 5	$0.00011	$0.00432
Sonnet 5	$0.00004	$0.00173
Haiku 4.5	$0.00002	$0.00086

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

Security

Grade A, and why

persisting-progress-across-sessions 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 10d 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.

skills/core/persisting-progress-across-sessions/SKILL.md · 108 lines

How it starts

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

Persisting Progress Across Sessions

Use this skill when a session ends mid-orchestration (context compaction, manual restart, crash) and you need to resume without repeating completed work.

The Resume Protocol

Step 1 — Find the Incomplete MANIFEST

# List all in-progress features
ls .jonggrang/.output/features/

Look for a MANIFEST.yaml with status: running or status: paused. Read it:

cat .jonggrang/.output/features/{feature_id}/MANIFEST.yaml

Key fields to read:

current_phase — next phase to execute
active_phases — which phases this run is executing
phases — per-phase status (completed / failed / pending)
agents — which agents ran and their output paths
validation — review_passed, tests_passed, coverage_met

Step 2 — Reconstruct Context from Phase Outputs

Do NOT re-run completed phases. Read their outputs instead:

# Phase 7 output (architecture plan)
cat .jonggrang/.output/features/{feature_id}/07-lead-architecture-plan.json

# Phase 8 output (implementation)
cat .jonggrang/.output/features/{feature_id}/08-developer-{task_id}.json

# Any reviewer reports
cat .jonggrang/.output/features/{feature_id}/09-reviewer-report.json

Step 3 — Identify Resumption Point

current_phase in MANIFEST  →  start from this phase
phases[N].status == 'failed'  →  retry this phase
phases[N].status == 'completed'  →  skip, output already exists

Step 4 — Resume the Orchestration

Call orchestrating-feature with resume: true and the feature_id. Pass the reconstructed context as a summary — do NOT re-read all source code; trust the phase outputs.

Resuming feature: {feature_id}
Completed phases: 1, 2, 3, 4, 7, 8
Current phase: 9 (design-verification)
Architecture plan: [summary from 07-lead-architecture-plan.json]
Implementation: [summary from 08-developer.json]

Cross-Session State Guarantee

The MANIFEST survives session resets. The ephemeral state does NOT:

File	Survives reset?	Action on resume
`MANIFEST.yaml`	✅ Yes	Read to get current phase
`feedback-loop-state.json`	❌ No	Assume clean state, re-run review/test if dirty_bit lost
`compaction-state.json`	❌ No	Will be refreshed on next Task spawn
`session-roles.json`	❌ No	Will be re-populated on next session start

Read the full file on GitHub · 108 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.

10d ago First seen · 108 lines · 22 tokens per session scan A c5df11d63cd1

Subscribe to this mod's changes

persisting-progress-across-sessions is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 865 once invoked, about $0.0001 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-30.

Memory and context core

persistent-notes

Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".

awslabs/agentcore-samples · 32 tokens

capability-evolver

Self-evolution workflow for the agent. Before substantive work, recall past outcomes from evolution memory; while editing, detect improvement signals; at task end, record the outcome; when reusable, distill or search the EvoMap network for proven genes/capsules. Use when the user starts non-trivial work (a feature, a…

Dianel555/DSkills · 98 tokens

persisting-progress-across-sessions