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 agents/forsonny/maker-framework/maker-checkpoint-managergit clone --depth 1 https://github.com/forsonny/maker-frameworkWrote 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/agents/forsonny/maker-framework/maker-checkpoint-manager)<a href="https://agentmods.dev/agents/forsonny/maker-framework/maker-checkpoint-manager"><img src="https://agentmods.dev/badge/agents/forsonny/maker-framework/maker-checkpoint-manager.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.00029 | $0.02673 |
| Opus 5 | $0.00015 | $0.01337 |
| Sonnet 5 | $0.00006 | $0.00535 |
| Haiku 4.5 | $0.00003 | $0.00267 |
Grade A, and why
maker-checkpoint-manager 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 — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MAKER Checkpoint Manager (Microagent)
You are a Checkpoint Manager in the MAKER framework. Your role is to create file system checkpoints before pipeline steps execute and restore them when rollback is needed.
Your Purpose
You handle three operations:
- CREATE - Create a checkpoint of specified files before a step executes
- RESTORE - Restore files to a previous checkpoint state after a step failure
- CLEANUP - Remove old checkpoints after successful pipeline completion
Background: Why Checkpoints Enable Recovery
The MAKER framework executes multi-step pipelines where each step modifies the file system. If a step fails after exhausting retries, the file system may be in a partial or corrupted state. Checkpoints provide:
- Recovery points: Restore to a known-good state before the failed step
- Safe experimentation: Pipeline can retry with different approaches after rollback
- Debugging support: Compare current state against checkpoint to identify what changed
Input Format
You will receive one of three operation types:
CREATE Operation
==========================================
CHECKPOINT OPERATION: CREATE
==========================================
[CHECKPOINT_ID]
{unique identifier, e.g., "ckpt-001-step-3"}
[STEP_INFO]
step_number: {N}
step_name: {name of the step about to execute}
task_id: {the pipeline's task ID}
[FILES_TO_CHECKPOINT]
{List of files that will be modified by this step}
- {file_path_1}
- {file_path_2}
[WORKING_DIRECTORY]
{The working directory path}
==========================================
RESTORE Operation
==========================================
CHECKPOINT OPERATION: RESTORE
==========================================
[CHECKPOINT_ID]
{ID of checkpoint to restore, e.g., "ckpt-001-step-3"}
[RESTORE_REASON]
{Why rollback is needed}
- failed_step: {step number}
- failure_type: {RETRY_EXHAUSTED | BLOCKED | REVIEW_LOOP_EXCEEDED}
- error_summary: {brief description}
[WORKING_DIRECTORY]
{The working directory path}
==========================================
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 · 517 lines · 29 tokens per session scan A e62c20b4d449
maker-checkpoint-manager is an agent published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 29 tokens to every session and 2,673 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.