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 skills/sliday/harn/checkpointnpx skills add sliday/harn --skill checkpointgit clone --depth 1 https://github.com/sliday/harnWhat 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.00047 | $0.00682 |
| Opus 5 | $0.00023 | $0.00341 |
| Sonnet 5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
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 2d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a session-recovery scaffolding skill. When invoked, perform ALL four steps below in the current project root.
Step 1: Create LEARNED.md
If LEARNED.md does not already exist in the project root, create it with this template:
# Learned
Tricky problems encountered during this project. Read this before starting work.
## Patterns
<!-- Add patterns discovered during development -->
## Gotchas
<!-- Add surprising behaviors or non-obvious constraints -->
## Failed Approaches
<!-- Document what was tried and why it didn't work -->
If it already exists, leave it untouched and tell the user.
Step 2: Create CHECKPOINT.json
If CHECKPOINT.json does not already exist in the project root, create it with this template:
{
"last_updated": "",
"current_task": "",
"completed_tasks": [],
"blocked_on": "",
"context_notes": "",
"files_in_progress": []
}
If it already exists, leave it untouched and tell the user.
Step 3: Add SessionStart hook snippet
Check if hooks/session-start.sh exists in the project root.
- If it exists, append the checkpoint-detection block below (only if it is not already present).
- If it does not exist, create
hooks/session-start.shwith the block.
Make the file executable (chmod +x).
# --- Harn Checkpoint Resume ---
# Why: https://harn.app/kb/context.html — "Structured note-taking"
if [ -f "${PROJECT_ROOT}/CHECKPOINT.json" ]; then
if ! jq empty "${PROJECT_ROOT}/CHECKPOINT.json" 2>/dev/null; then
echo "Harn: CHECKPOINT.json is malformed — ignoring" >&2
else
TASK=$(jq -r '.current_task // empty' "${PROJECT_ROOT}/CHECKPOINT.json" 2>/dev/null)
if [ -n "$TASK" ]; then
echo "Harn: Resuming — last task: ${TASK}" >&2
fi
fi
fi
# --- End Checkpoint Resume ---
Step 4: Suggest AGENTS.md addition
Print the following block and instruct the user to add it to their AGENTS.md (or offer to append it automatically if the file exists):
## Session Recovery
- Before starting: read LEARNED.md for gotchas
- After compact: read CHECKPOINT.json for current state
- When learning something tricky: update LEARNED.md
- Before finishing a sub-task: update CHECKPOINT.json
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.
- 2d ago First seen · 89 lines · 47 tokens per session scan A c762c5129a06
checkpoint is a skill published in the GitHub repository sliday/harn (5 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 682 once invoked, about $0.0002 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 skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后,主动执行此流程! 将学到的经验归档为 skill,供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.