chain-load

A command that loads the latest saved chain link for a project. It restores notes from an earlier session so work can continue with its previous context.

In plain words
What is it for?
Use it to resume a named chain, inspect recent links, and identify missing or stale information before continuing.
Why use it?
It reduces the chance of missing earlier decisions, pending tasks, or known gaps when returning to a project.

Command

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.

agentmods
npx agentmods add commands/deevsdeevs/agent-system/chain-load
Clone the repo
git clone --depth 1 https://github.com/DeevsDeevs/agent-system
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 382 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00382
Opus 5 $0.00000 $0.00191
Sonnet 5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured 2d ago against content hash af07e0f23003, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

chain-load 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.

chain-system/commands/chain-load.md · 39 lines

What it actually says

Loads the most recent chain link to continue work from a previous session.

Chain name: $ARGUMENTS

If no chain name provided, ask the user which chain to load (suggest using /chain-list).

Steps

  1. Check chain exists and find most recent link (by timestamp in filename):
ls .claude/chains/[chain-name]/*.md 2>/dev/null | sort -r | head -1

If no result, inform user chain doesn't exist and suggest /chain-list.

  1. Read the file fully - this is your working context

  2. List the 5 most recent links:

ls .claude/chains/[chain-name]/*.md 2>/dev/null | sort -r | head -5
  1. Detect Insufficiency - check for gaps requiring user input:

    • Missing Context: Link references files/decisions not captured. Ask: "Link references [X] - verify current state?"
    • Ambiguous Next-Steps: "Next Step" is vague. Ask: "Next step unclear: [quote]. What specifically?"
    • Stale Data: Link older than 7 days. Ask: "Link [N] days old. Project diverged?"

    If ANY gap detected: STOP. Interview user. No interpolation or assumptions.

  2. Show the user:

    • Chain name and most recent link filename
    • Brief summary (from Readable Summary if present)
    • Next Step from loaded file
    • Insufficiency flags with specific questions (if any)
    • List of 5 most recent links
  3. If gaps flagged, clarify before proceeding. Otherwise ask about loading additional links

Note: Fully internalize the loaded content - it's your working context. Only show the user a brief summary.

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. 2d ago First seen · 39 lines · 0 tokens per session scan A af07e0f23003

Subscribe to this mod's changes

chain-load is a command published in the GitHub repository DeevsDeevs/agent-system (40 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 382 tokens. 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.