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 vikcena01/ai-continuity-plugin --skill continuitygit clone --depth 1 https://github.com/vikcena01/ai-continuity-pluginWrote 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/vikcena01/ai-continuity-plugin/continuity)<a href="https://agentmods.dev/skills/vikcena01/ai-continuity-plugin/continuity"><img src="https://agentmods.dev/badge/skills/vikcena01/ai-continuity-plugin/continuity/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.
<a href="https://agentmods.dev/skills/vikcena01/ai-continuity-plugin/continuity"><img src="https://agentmods.dev/badge/skills/vikcena01/ai-continuity-plugin/continuity.svg" alt="Reviewed on agentmods" width="80" 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.00072 | $0.00797 |
| Opus 5.5 | $0.00029 | $0.00319 |
| Sonnet 5.5 | $0.00014 | $0.00159 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
continuity 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuity — keep long-running project state
A continuity MCP server stores durable project state (decisions, constraints, rejected alternatives, open questions, next steps) as versioned claims. Your job is to keep it current and to honor it — so a future session resumes correctly instead of re-litigating settled decisions.
At the start of a session on an ongoing project
Call resume_context (pass project if the user names one). Treat the result as authoritative:
- 🔒 FROZEN items must not be changed or reopened.
- 🚫 Do NOT revisit items are already rejected — do not re-propose them.
- Continue from the Resume at next step.
If nothing is returned and the work is clearly a new ongoing project, offer to
create_project.
While working — capture autonomously (do not ask permission)
Default to capturing NOTHING. Most turns warrant nothing. Record only what a future session could not re-derive, in one of these shapes:
- A decision the user settles on →
record_decision(include the reasoning in the body). - A constraint future work must respect →
record_constraint. - An alternative considered and rejected →
record_rejectionwith the reason. A rejection without a reason is refused: the reason is what stops it being re-proposed. - An open question, risk, milestone, or next action →
record_open. - FRAMING — a statement setting strategy or what matters ("X is the moat", "Y is the real bottleneck"). These do not look like decisions and are the most commonly missed. Record as a decision.
- A STANDING INSTRUCTION about how to operate or who decides ("never do X without asking", "you have full ownership"). Record as a constraint, never as a question — a question reads as an open topic rather than a rule to obey.
Do NOT record: your own explanations, restatements of existing claims, progress narration, or a rewrite of the next step unless the next step actually changed. Prefer superseding an existing claim over adding a near-duplicate, and keep bodies short — they are re-read in every future session. If in doubt, stop without capturing.
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.
- 1mo ago Changed · +20 lines 53701834756c
- 1mo ago First seen · 39 lines · 72 tokens per session scan A 6b5bd7540fe4
continuity is a skill published in the GitHub repository vikcena01/ai-continuity-plugin (5 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 797 once invoked, about $0.0003 per session on Opus 5.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
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.
wicked-garden-repo-learn
Learn an unfamiliar repo the way a senior engineer does: follow where the code actually churns, find what that churn touches that the rest of the system leans on, read the load-bearing code for real, then write down BOTH what you learned (knowledge) and what should hold (policies) — as inert estate proposals a human…
entire
How to use the Entire CLI (checkpoints, search, sessions, and more). Use whenever a task involves entire, checkpoints, or the entire command.
session-handoff-number-collision-with-unmerged-sibling
Detect and recover from a session-number collision when running session-handoff and a parallel/sibling session has authored a same-numbered handoff doc that hasn't merged into main yet. Use when: (1) you're in session-handoff Phase 1 about to write docs/handoffs/sessionNNNhandoff.md, (2) ls docs/handoffs/ shows the…
context-guard
Installs Claude Code hooks that keep AI context files fresh. Two-tier enforcement — Tier 1 nudges at session end, Tier 2 blocks commits when structural files are staged without context updates. Includes content filter, drift check, structural change reminder, SessionStart health check, and the context-updater agent.
rk-push
Push local knowledge base to the remote repository. Always fetches remote first, Agent compares diffs and merges (alias LRU merge for index.md, union dedup for registry.md, newer-cached-date wins for docs), then commits and pushes. Retries once on push rejection. Use when user says 'push knowledge', 'sync to remote'…