install

An installer for Rekal, a Git-backed memory tool that records why changes were made, what was tried, and what was rejected in earlier AI sessions.

In plain words
What is it for?
Use it when Rekal is missing from the command line and you need to install its binary before setting up a repository.
Why use it?
It puts the Rekal command on the machine so repositories can use that history across coding sessions.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/rekal-dev/rekal-cli/install
Any agent
npx skills add rekal-dev/rekal-cli --skill install
Clone the repo
git clone --depth 1 https://github.com/rekal-dev/rekal-cli

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 411 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.00411
Opus 5 $0.00033 $0.00205
Sonnet 5 $0.00013 $0.00082
Haiku 4.5 $0.00007 $0.00041

Measured 2d ago against content hash 8a10847b3b9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

plugin/skills/install/SKILL.md · 55 lines

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.

Changes

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.

  1. 2d ago First seen · 55 lines · 66 tokens per session scan A 8a10847b3b9a

Subscribe to this mod's changes

install is a skill published in the GitHub repository rekal-dev/rekal-cli (140 stars, last pushed 28d ago), licensed Apache-2.0. It adds 66 tokens to every session and 411 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.

Related

Other skills, from other repositories