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/opencoven/coven/memory-timeline-managernpx skills add OpenCoven/coven --skill memory-timeline-managergit clone --depth 1 https://github.com/OpenCoven/covenWrote 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/opencoven/coven/memory-timeline-manager)<a href="https://agentmods.dev/skills/opencoven/coven/memory-timeline-manager"><img src="https://agentmods.dev/badge/skills/opencoven/coven/memory-timeline-manager.svg" alt="Measured on agentmods" 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.00058 | $0.00566 |
| Opus 5 | $0.00029 | $0.00283 |
| Sonnet 5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
memory-timeline-manager 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Timeline Manager
Use this skill for the memory workflow:
- Capture quickly in
memory/YYYY-MM-DD.md - Curate durable facts in
MEMORY.md - Promote important snippets from timeline to long-term memory
- Keep changes safe and reversible
Safety rules (always)
- Allowed write targets:
MEMORY.mdmemory/*.md
- Never write outside those paths unless user explicitly asks.
- Prefer additive edits over destructive rewrites.
- Before deleting or bulk-pruning memory files, ask for confirmation.
- For uncertain/large edits, create a dated backup file in
memory/first.
Fast routing
- "remember this" / daily logs / quick note → append to
memory/YYYY-MM-DD.md - stable preferences / decisions / recurring schedule / project truths →
MEMORY.md - "promote this" → append snippet to
MEMORY.mdwith timestamp heading - cleanup/review requests → follow retention sweep in
references/retention.md
Standard operations
1) Capture timeline note
- Target file:
memory/<today>.md - If file missing, create it with a date heading.
- Append concise bullet(s), preserving chronology.
2) Promote snippet to long-term memory
Use scripts/promote_snippet.py when available for deterministic formatting.
- Add heading:
## Promoted from Timeline (YYYY-MM-DD HH:MM:SS) - Add cleaned snippet text.
- Keep entries short and factual.
3) Retention labeling (lightweight)
Use labels in note text or sidecar metadata when requested:
keepreviewarchivedelete-candidate
When labels are in text, use [#label] suffix on bullets for compatibility.
4) Weekly review sweep
- Read recent
memory/YYYY-MM-DD.mdfiles - Identify durable items worth keeping
- Promote to
MEMORY.md - Optionally mark stale notes as
archive/delete-candidate
See references/retention.md for checklist.
File conventions
- Timeline files:
memory/YYYY-MM-DD.md - Long-term memory:
MEMORY.md - Avoid creating extra docs unless user asks.
References
What ships with it
3 files 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.
- 5d ago First seen · 77 lines · 58 tokens per session scan A 69ee89c6c13e
memory-timeline-manager is a skill published in the GitHub repository OpenCoven/coven (46 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 566 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
handoff
Write a compact, decision-ready handoff so the next session (or the user) can continue without reconstructing the current one. Use when the session is ending, context is running low, the user asks for a handoff / "pass the baton" / "hand off", or a long-running operation needs a durable state checkpoint.
cao-learning
Report task outcomes and distill lessons so the team improves across runs — reportoutcome after each unit of work, retrospector handoffs at natural boundaries, and applying injected lessons. Use in workflows that run repeatedly over similar work items. Requires memory.learningenabled; degrade silently when the tools…
cao-memory
Store, recall, and forget durable facts with CAO memory — user preferences, project conventions, decisions, and corrections that should persist across sessions and agents. Use proactively to check memory before asking the user, and to save anything worth remembering. Distinct from any provider-native memory.
mem0-integration
Mem0 memory layer integration for AI agents. Implement persistent, semantic memory for long-term context retention and personalization.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
persistent-memory
Observation capture and retrieval across sessions. Stores decisions, discoveries, and bugfix patterns. Searchable via tags and relevance scoring.