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 skills add avizmarlon/agent-skills --skill agent-continuity-loopgit clone --depth 1 https://github.com/avizmarlon/agent-skillsWrote 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/skills/avizmarlon/agent-skills/agent-continuity-loop)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/agent-continuity-loop"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/agent-continuity-loop.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.1 | $0.00073 | $0.02260 |
| Opus 5 | $0.00036 | $0.01130 |
| Sonnet 5 | $0.00015 | $0.00452 |
| Haiku 4.5 | $0.00007 | $0.00226 |
Grade A, and why
agent-continuity-loop 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 6d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Continuity Loop
Use this as the reusable handoff loop for substantial work that spans sessions, agents, branches, or PRs. The goal is continuity without ceremony: a future blind AI should be able to reopen the repo, read the living docs, verify current state, and continue without relying on chat memory.
Trigger Triage
Run the full loop when the task changes project state, code, config, business status, roadmap, spec, evidence, branch/PR state, or the next session's work.
Skip the full loop for trivial one-off work: a single command, short translation, small answer, read-only check with no durable decision, or urgent one-command operation. If in doubt, do the smallest useful version: verify reality, work, and leave a brief handoff note only if future work needs it.
Relationship To new-project
Use new-project before this skill when starting a new project, repo, feature,
build, or phase kickoff. new-project is the foundation gate that consults the
engineering and business standards.
Use this skill after the project already exists, when continuing work or closing
a session. If the continuity pass discovers missing charter, spec, ADR, metrics,
roadmap, or engineering gates for a new phase, invoke new-project or the
specific missing standard instead of duplicating that checklist here.
Start Or Resume
- Load project instructions first:
AGENTS.md,CLAUDE.md,GEMINI.md, and any repo-local workflow file such asdocs/ai-workflow.md. - Load living docs in the repo-defined order. If no order exists, use these
candidates:
session-handoff.md,SESSION-HANDOFF.md,PROGRESS.md,README.md,CHANGELOG.md,docs/roadmap.md,docs/SPEC.md,docs/specs/,docs/adr/,docs/engineering-gates.md, anddocs/launch/. - Verify reality before trusting docs: run
git status --short --branch,git status --porcelain, current branch, latest commit, and remotes. - If a forge remote exists and the task touches integration, inspect relevant open PRs before editing.
- Treat docs and previous prompts as hypotheses. Current code, current git state, current PR state, and freshly verified external sources win.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 195 lines · 73 tokens per session scan A a5952cb5c3f0
agent-continuity-loop is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 2,260 once invoked, about $0.0004 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
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
notebooklm-manager
Manages NotebookLM notebooks — query, add, list, search, enable/disable, remove. Use when a notebooklm.google.com URL appears or user mentions NotebookLM. Handles URLs through its own Chrome agent — do not navigate directly. Requires: claude-in-chrome MCP.
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.
morning-triage
Discovery for an autonomous loop — find this turn's work instead of being handed it. Reads what changed since the last run (failed CI, new issues, merged commits), judges what's actually worth acting on, writes findings to a durable state file, and hands each off to the SDLC loop with a stop-condition. Use as the…
eco-max
Maximum-savings variant of /eco - the same frugality rules PLUS a low reasoning-effort override for the invoked task. Use for routine chores (rename, small fix, quick question, boilerplate) when the user wants absolute minimum token spend; prefer plain /eco for hard or high-stakes work. Works in any language.
keel-handover
Add this session's block to HANDOVER.md before ending or compacting — done / tried-failed / latest / next. Rotates via /keel-distill when the 3-block cap is hit.