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/vikcena01/ai-continuity-plugin/continuitynpx skills add vikcena01/ai-continuity-plugin --skill continuitygit clone --depth 1 https://github.com/vikcena01/ai-continuity-pluginWhat 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.00072 | $0.00498 |
| Opus 5 | $0.00036 | $0.00249 |
| Sonnet 5 | $0.00014 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
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 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.
What it actually says
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)
As the conversation produces durable facts, record them right away:
- 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. - An open question, risk, milestone, or next action →
record_open. Keep each claim to one crisp fact. Capture is non-destructive and reviewed later via git, so err toward capturing rather than skipping. Do not capture idle chatter — only things a future session would need to continue correctly.
Deliberate acts — only on explicit user request
- "freeze X" / "lock X" →
freeze_claim. - "why did we change X?" →
why.
Principles
- Record the REASON, not just the decision — a future session must know why a path was chosen or rejected, or it will be argued back into a reversal.
- Never silently contradict a frozen claim. If the user's new direction conflicts with a frozen item, surface the conflict and confirm before proceeding.
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 · 39 lines · 72 tokens per session scan A 6b5bd7540fe4
continuity is a skill published in the GitHub repository vikcena01/ai-continuity-plugin (2 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 498 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
status
Use when the user wants a one-screen view of current hyperflow project state — version, profile freshness, memory count, and live progress on every in-flight task. Read-only; never modifies state, never dispatches workers. Trigger with /hyperflow:status, "what is hyperflow doing", "show task progress", "where are we".
cache
Use when the user wants to view, search, add, edit, prune, archive, or clear hyperflow memory entries. CRUD interface for .hyperflow/memory/ — never modifies source code, only memory files. Trigger with /hyperflow:cache, "show memory", "search memory for X", "clear memory", "what does hyperflow remember about Y".
treework-manual
Use TreeWork Manual when the user asks for it, or when the Agent judges that organizing ongoing, multi-part work as a persistent Markdown Tree would improve direction, continuity, recovery, or handoff. Adapt the Tree's depth and document detail to the user's needs, domain, and situation rather than a fixed threshold.
treework
Use TreeWork, a tree-guided development plugin for complex or evolving software projects that need staged alignment, pre-coding technical Specs, declarative project-tree planning, branch-scoped Git worktrees, durable recovery, and protected completion. It teaches the Agent to move through development along the Tree…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.