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 NovasPlace/CSM --skill csm-continuitygit clone --depth 1 https://github.com/NovasPlace/CSMWrote 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/novasplace/csm/csm-continuity)<a href="https://agentmods.dev/skills/novasplace/csm/csm-continuity"><img src="https://agentmods.dev/badge/skills/novasplace/csm/csm-continuity.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 22 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00060 | $0.00681 |
| Opus 5 | $0.00030 | $0.00341 |
| Sonnet 5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
csm-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 8d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSM Continuity
Use the plugin's full CSM runtime without treating memory as more authoritative than the current workspace. Native hooks automatically capture session, prompt, tool, compaction, subagent, and stop events; do not duplicate routine hook capture manually.
Start or resume work
- Resolve
projectRootto the current workspace root. Keep every read and write scoped to it. - Call
csm_runtime_statusbefore the first memory operation. If the runtime is unavailable or points at the wrong provider, stop and report the configuration problem. - If the injected onboarding and
<agent_reentry_context>are insufficient, callcsm_onboard_agent,csm_reentry_preview, orbridge_resume_contextwithprojectRootand the user's current task. - Use
csm_memory_search,csm_memory_context,recall_lessons, orget_context_briefonly when the resumed context needs focused evidence. - Verify recalled claims against current files, tests, and user instructions before acting on them.
Preserve useful state
- Native tool hooks already record tool evidence, work-journal entries, experience packets, AgentBook events, and living-state triggers. Use
bridge_sync_turnonly for an additional durable milestone that automatic capture cannot infer. - Use
memory_lessonfor a reusable lesson andsave_memoryfor an explicitly useful durable record. - Never persist credentials, secrets, access tokens, private keys, or unnecessary sensitive content. Redact before saving.
- Prefer evidence and provenance over broad claims. Current repository state remains the source of truth.
Checkpoint and hand off
- Before compaction, interruption, or a risky transition, inspect
csm_context_pressurewhen an explicit message snapshot is available. - Use
create_checkpointwhen the current state would be expensive to reconstruct. - Before stopping or transferring work, sync the final durable milestone and call
bridge_handoff_summary. - Make the handoff concrete: outcome, files changed, verification, open risks, and next action.
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.
- 8d ago First seen · 44 lines · 60 tokens per session scan A a3ed8622fbfa
csm-continuity is a skill published in the GitHub repository NovasPlace/CSM (42 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 681 once invoked, about $0.0003 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-30.
Other skills, from other repositories
dark-memory
Use for governance, memory, drift detection, and audit trail via dark-memory-mcp. Covers 52 canonical + 3 red-team tools across 16 namespaces: session lifecycle, agentmemory CRUD+search, vibe-flow spec/artifact publish + drift, LLM-as-judge, delegation+mindset, research, observability, error observatory, governance…
mem9
Persistent cloud memory plugin for OpenClaw. This document routes setup, troubleshooting, and uninstall flows and defines config boundaries.
usage
Wren Engine CLI workflow guide for AI agents. Answer data questions end-to-end using the wren CLI: gather schema context, recall past queries, write SQL through the MDL semantic layer, execute, and learn from confirmed results. Use when: user asks a data question, requests a report or analysis, asks about metrics…
kip-cognitive-nexus
Persistent graph-based memory for AI agents via KIP (Knowledge Interaction Protocol). Provides retrieval-first memory operations (KQL), durable writes (KML), schema discovery (META), and memory hygiene patterns. Use whenever the agent needs to consult or update persistent memory, especially for: remembering user…
mstar-compound-refresh
A knowledge-maintenance workflow for reviewing project knowledge documents, removing outdated material, merging overlaps, or creating a starter knowledge set from a codebase.
add-editor
Wire Deus's memory + evolution layers into an external code editor (Zed and other ACP/MCP clients) so the editor's own agent gains Deus's vault recall and self-improving reflexion loop. Configuration only — no new code. Triggers on "add editor", "use Deus in my editor", "zed integration", "editor integration", "wire…