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 rekal-dev/rekal-cli --skill installgit clone --depth 1 https://github.com/rekal-dev/rekal-cliWrote 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/rekal-dev/rekal-cli/install)<a href="https://agentmods.dev/skills/rekal-dev/rekal-cli/install"><img src="https://agentmods.dev/badge/skills/rekal-dev/rekal-cli/install/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/rekal-dev/rekal-cli/install"><img src="https://agentmods.dev/badge/skills/rekal-dev/rekal-cli/install.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.00066 | $0.00411 |
| Opus 5.5 | $0.00026 | $0.00164 |
| Sonnet 5.5 | $0.00013 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
install 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.
What it actually says
Install Rekal
Rekal is git-backed memory of prior AI sessions: why a change was made, what was
tried, what was rejected. This installs the binary. Setting up a repository is a
separate step — the init skill.
Ask first
The installer downloads a release archive and writes an executable to the user's machine. Say that plainly, then wait for an answer.
If the user declines, stop. Say Rekal is not available and answer from the tree. Declining is a complete answer.
Run it
The plugin ships the installer on PATH:
rekal-install
That is a vendored copy of the project's own scripts/install.sh — it detects
the platform, downloads the matching release from GitHub, and verifies it
against the published checksums. Installs to ~/.local/bin; pass
--target <dir> to override.
Requires git, macOS or Linux. The archive is large (~160 MB — the binary embeds an embedding model), so the download takes a moment.
Verify
rekal version
If the shell reports command not found after a successful install, the install
directory is not on PATH. Tell the user which directory to add and let them
edit their own shell profile. Do not edit it for them.
Next
The binary is installed but no repository uses it yet. If the user wants memory
in the current repo, continue with the init skill. Ask before running it —
that is a separate decision about a separate thing.
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 · 55 lines · 66 tokens per session scan A 8a10847b3b9a
install is a skill published in the GitHub repository rekal-dev/rekal-cli (205 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 411 once invoked, about $0.0003 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
context-engineering
Use when designing, reviewing, or debugging how an agent's context window gets filled, pruned, or shared — choosing what loads at boot versus on demand, sizing an install or an always-loaded file, fixing an agent that drifts, repeats itself, or forgets constraints mid-task, planning compaction or summarization…
claude-compaction-restore
Use when a Claude Code session is about to compact, has just compacted, reached its context limit, resumed after /compact, or must rebuild its working picture of a long-running seat from its own restore map, its JSONL transcript and the files it touched.
retiring-and-inheriting-a-seat
Use when you are a sitting agent near your context threshold (85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure)…
session-compaction-and-restore
Use when reasoning about what survives compaction/context-loss/restart/seat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent graph-based memory. Recall context before responding, remember insights after. Each group has private memory; global memory is read-only.