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 Cfvillarroel/carryover --skill skillgit clone --depth 1 https://github.com/Cfvillarroel/carryoverWrote 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/cfvillarroel/carryover/skill)<a href="https://agentmods.dev/skills/cfvillarroel/carryover/skill"><img src="https://agentmods.dev/badge/skills/cfvillarroel/carryover/skill/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/cfvillarroel/carryover/skill"><img src="https://agentmods.dev/badge/skills/cfvillarroel/carryover/skill.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.00027 | $0.01545 |
| Opus 5.5 | $0.00011 | $0.00618 |
| Sonnet 5.5 | $0.00005 | $0.00309 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
carryover 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
carryover
carryover is a local, cross-tool memory layer:
one SQLite store (~/.headroom/memory.db with headroom, else ~/.carryover/memory.db) shared by
Claude Code, Codex, Cursor and Hermes. It holds memories (facts + typed entities +
relationships, indexed by repo), per-repo auto-wikis, !macro playbooks, a cross-workspace
inbox, and materializes everything into an Obsidian vault.
Everything runs on this machine. No network, no telemetry.
What is already automatic
Once hermes/install-hermes.sh has run, two shell hooks do this without being asked:
pre_llm_call— on a session's first turn injects what carryover knows about the repo incwd(its group) plus a fewgeneralfacts; every turn it delivers pending workspace messages and expands any!playbooknamed in the prompt; after edits it raises the save-what-mattered prompt.post_tool_call— flags the session as "files changed" afterwrite_file/patch/terminal.
So do not run a recall command just to see the repo's context at the start of a session — it is already in your prompt. Reach for the commands below when you need more than that.
Recall
| Need | Do |
|---|---|
| Anything beyond the injected bullets | co-recall "<query>" (this repo's group) · co-recall --all "<query>" |
| From an MCP client / another repo's knowledge | the mcp_carryover_recall tool (repo arg scopes it; omit for all repos) |
| Structural questions — what links to X, hub entities, notes mentioning X and Y | grep the vault, not the store: ~/Documents/carryover-vault/knowledge/*.md (frontmatter id/repo/entities) and entities/*.md ([[backlinks]]) |
Recall is semantic when headroom is installed, keyword otherwise (co-mem backend says which).
Saving
Prefer structured saves — each fact becomes its own searchable memory and the entities/relationships build the graph:
mem-save --json '{"content":"1-line summary",
"facts":["atomic, self-contained facts"],
"entities":[{"entity":"X","type":"project|tech|person|concept"}],
"relationships":[{"source":"X","relationship":"uses","destination":"Y"}],
"category":"area","tags":["…"],"importance":0.7}'
mem-save "plain text" # when structuring isn't worth it
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 First seen · 129 lines · 27 tokens per session scan A 2544dc1ba3bb
carryover is a skill published in the GitHub repository Cfvillarroel/carryover (5 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,545 once invoked, about $0.0001 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
context-window-hygiene
Manage what enters and stays in the context window — pruning, compaction, summary fidelity, ordering — so the agent stays coherent on long runs without inflating cost. Use when the user is hitting context limits, running long agentic loops, paying for full-history replays, or asks "how do I keep context manageable?" /…
memory-design
Design memory for an LLM agent — what to keep, where to keep it, and when memory hurts more than it helps. Use when the user is adding memory to an agent and mentions short-term memory, long-term memory, episodic, semantic, conversation history, summary memory, vector memory, memory store, mem0, Letta, MemGPT, or asks…
identity-snapshot
Generate a living profile of the user's working patterns, decision tendencies and quality preferences from their Dex data. Use when the user says 'what are my patterns', 'how do I work', or during week-review. Also use proactively when the model (older than 7 days) is stale. Not for planning a week; use week-plan.
reset
Re-run the setup questions over an existing Dex vault when preferences or setup answers changed, without losing data. Use when the user says 'restructure my Dex', 'redo my setup', 'my pillars are wrong now'. Not for a job or role change; use change-job — it runs this same reset plus the people, archive and task…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
session-restore
Context restoration from .jsonl session backups. Parses history, builds chronology, saves key decisions to memory.