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.
git 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/commands/cfvillarroel/carryover/vault)<a href="https://agentmods.dev/commands/cfvillarroel/carryover/vault"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/vault/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/commands/cfvillarroel/carryover/vault"><img src="https://agentmods.dev/badge/commands/cfvillarroel/carryover/vault.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.00017 | $0.00187 |
| Opus 5 | $0.00009 | $0.00093 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
vault 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 9d 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
Build or refresh the unified Obsidian vault. Run via Bash:
bash ~/.carryover/vault-gen.sh
Then tell the user: it wrote ~/Documents/carryover-vault (a visible folder, and it registers the
vault with Obsidian so it shows up in the vault switcher) — open it in Obsidian to browse every
memory as a note, the entity/relationship graph in the graph view, and each registered repo's wiki,
all together. It's two-way: editing a memory note's first paragraph or its importance in Obsidian
syncs back to the store on the next co-vault (facts, entities, relationships and tags are derived
and regenerated, so they're read-only). No Obsidian plugins needed.
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.
- 9d ago First seen · 17 lines · 17 tokens per session scan A d5af765c1f4f
vault is a command published in the GitHub repository Cfvillarroel/carryover (5 stars, last pushed 24d ago), licensed MIT. It adds 17 tokens to every session and 187 once invoked, about $0.0001 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 commands, from other repositories
context-restore
Expert Context Restoration Specialist focused on intelligent, semantic-aware context retrieval and reconstruction across complex multi-agent AI workflows. Specializes in preserving and reconstructing project knowledge with high fidelity and minimal information loss.
context-save
An elite context engineering specialist focused on comprehensive, semantic, and dynamically adaptable context preservation across AI workflows. This tool orchestrates advanced context capture, serialization, and retrieval strategies to maintain institutional knowledge and enable seamless multi-session collaboration.
AGENTS
The thirteen memory slash commands, registered once by the memory component through register.ts (registerMemoryCommands(pi, deps)). MEMORYCOMMANDNAMES: /memory /memfs /remember /init /doctor /recompile /memory-repository /sleeptime /reflect /dream /search /people /facts. Score 24 (53 files, DI surface, central…
demo-consume-context
Worked example: discover, load, and tag an approved context package, then write a reverse-index addendum. Proves the produce/consume/tag loop end-to-end. Not for real feature work.
institutional-memory-distill
Distill decisions, reasoning, and rejected alternatives from PRs, design docs, and postmortems into the project's decisionledger, so ult-context-generate's trip-wire can surface institutional memory before new work quietly repeats settled ground. Do NOT use to query the ledger against new work or decide…
gaai-ask
Search workspace memory — ranked entries with 1-hop graph context (cognitive guarantee).