Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cukas/remembrall/plugin install remembrallWrote 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/cukas/remembrall/timeturner)<a href="https://agentmods.dev/skills/cukas/remembrall/timeturner"><img src="https://agentmods.dev/badge/skills/cukas/remembrall/timeturner.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.00043 | $0.00996 |
| Opus 5 | $0.00022 | $0.00498 |
| Sonnet 5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade C, and why
timeturner scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "/tmp/remembrall-timeturner/${SESSION_ID}" How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Time-Turner — Parallel Agent Manager
Manage Time-Turner agents that were spawned to continue work in parallel.
Sub-commands
Parse the user's argument to determine which sub-command to run.
/timeturner status (default if no argument)
Show the current Time-Turner state:
REMEMBRALL_ROOT="${CLAUDE_PLUGIN_ROOT:-$(cat /tmp/remembrall-meta/plugin-root 2>/dev/null)}"
bash "$REMEMBRALL_ROOT/hooks/time-turner-check.sh" "$(pwd)"
If the script exits 1 (no active Time-Turner), tell the user: "No active Time-Turner found."
/timeturner diff
Show what the Time-Turner agent changed:
# Find completed Time-Turner
for d in /tmp/remembrall-timeturner/*/; do
[ -f "$d/status" ] || continue
STATUS=$(cat "$d/status")
[ "$STATUS" = "completed" ] || continue
WORKTREE="$d/worktree"
cd "$WORKTREE" && git diff HEAD
break
done
If no completed Time-Turner is found, run /timeturner status instead and tell the user to wait.
/timeturner merge
- Show the diff for user review (run the diff sub-command above)
- Ask the user to confirm before merging: "Apply these changes to your working branch?"
- Find the main repo CWD and session ID:
for d in /tmp/remembrall-timeturner/*/; do [ -f "$d/status" ] || continue STATUS=$(cat "$d/status") [ "$STATUS" = "completed" ] || continue SESSION_ID=$(basename "$d") WORKTREE="$d/worktree" break done - In the main repo, attempt merge:
git -C "$(pwd)" merge --no-commit "timeturner/${SESSION_ID}" - If clean merge (exit 0) → commit with
[Time-Turner]prefix:git -C "$(pwd)" commit -m "[Time-Turner] Apply parallel agent changes from session ${SESSION_ID}" - If conflicts (exit non-zero) → warn the user, abort merge, suggest manual resolution:
Tell the user which files have conflicts and how to resolve manually.git -C "$(pwd)" merge --abort 2>/dev/null || true - Clean up regardless of outcome on success:
git -C "$(pwd)" worktree remove "$WORKTREE" 2>/dev/null || true git -C "$(pwd)" branch -d "timeturner/${SESSION_ID}" 2>/dev/null || true rm -rf "/tmp/remembrall-timeturner/${SESSION_ID}"
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.
- 7d ago First seen · 115 lines · 43 tokens per session scan C f33f5fa1e5c0
timeturner is a skill published in the GitHub repository cukas/remembrall (6 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 996 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…