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 Ariestar/sivtr --skill sivtr-memorygit clone --depth 1 https://github.com/Ariestar/sivtrWrote 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/ariestar/sivtr/sivtr-memory)<a href="https://agentmods.dev/skills/ariestar/sivtr/sivtr-memory"><img src="https://agentmods.dev/badge/skills/ariestar/sivtr/sivtr-memory/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/ariestar/sivtr/sivtr-memory"><img src="https://agentmods.dev/badge/skills/ariestar/sivtr/sivtr-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.02717 |
| Opus 5.5 | $0.00018 | $0.01087 |
| Sonnet 5.5 | $0.00009 | $0.00543 |
| Haiku 4.5 | $0.00005 | $0.00272 |
Grade A, and why
sivtr-memory 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sivtr Memory
Sivtr is the shared local work memory for this machine.
Use it before asking the user to paste logs, repeat decisions, or restate earlier work.
Core rule:
Search for evidence first. Expand only the smallest relevant context. Ask when memory is missing, ambiguous, stale, or permission is required.
MCP tools (preferred when available)
If the host exposes sivtr MCP tools, prefer them over shelling out to the CLI. Register with:
sivtr mcp install -y
| Tool | Use |
|---|---|
sivtr_search |
Narrow search over terminal / agent / provider / desk:... |
sivtr_show |
Expand a ref or @last / @name |
sivtr_zoom |
Neighboring record context |
sivtr_filter |
Narrow @last or a saved set |
sivtr_status |
Hooks, providers, daemon, local workspace origins (ws), remotes, vars |
sivtr_usage |
Token usage and exact model costs from the archive |
sivtr_stats |
Archive activity, quality findings, and usage statistics |
Fall back to CLI commands below when MCP is not configured.
When to Use
Use this skill whenever local work memory may contain useful evidence. Sivtr retrieves recent terminal activity, AI conversation history, prior decisions, validation output, debugging trails, and handoff context.
Use it before asking the user to repeat context when you need to know things like:
- what just happened in the terminal or an agent session
- what command was run, what output it produced, or whether validation passed
- what the user or a previous agent decided, rejected, or planned
- where earlier debugging, build, test, lint, deploy, or research work left off
- what evidence supports a recap, handoff, status update, or next step
- whether missing or truncated current-context output exists in local memory
Do not use Sivtr as truth by itself. Treat memory as evidence to retrieve, then verify current files or commands before making claims about current state.
Default Retrieval Workflow
Mental model to keep in mind:
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.
- 1mo ago Changed · +2 lines 98b05f323e99
- 1mo ago First seen · 170 lines · 46 tokens per session scan A 1d912e57c553
sivtr-memory is a skill published in the GitHub repository Ariestar/sivtr (257 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 2,717 once invoked, about $0.0002 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-30.
Other skills, from other repositories
doris-debug-resource-isolation
Use for Doris Workload Group / resource tag queue starvation, CPU/memory isolation leaks, and workload policy debugging. Commands: SHOW WORKLOAD GROUPS, EXPLAIN resource.
remem
Use when the user asks Codex to recall prior project context, save durable decisions or bug fixes, inspect remem memory health, or activate remem automatic memory hooks from the Codex plugin.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
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.
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.