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 initgit 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/init)<a href="https://agentmods.dev/skills/rekal-dev/rekal-cli/init"><img src="https://agentmods.dev/badge/skills/rekal-dev/rekal-cli/init/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/init"><img src="https://agentmods.dev/badge/skills/rekal-dev/rekal-cli/init.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.00075 | $0.00550 |
| Opus 5.5 | $0.00030 | $0.00220 |
| Sonnet 5.5 | $0.00015 | $0.00110 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
init 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
Initialize Rekal in this repository
Run once per repository. The binary must already be installed — if rekal is
not on PATH, use the install skill first.
Do not volunteer this
This skill is loaded in every repository the user opens. Almost none of them
should be initialized. Act when the user asks, or when a rekal command has
actually reported the repo is not initialized. A repository simply lacking
.rekal/ is not a reason to suggest anything.
Ask first
rekal init changes the user's repository. Name what it writes, then wait:
.rekal/— the store (two files: an append-onlydata.db, a localindex.db)- a
post-commit/pre-pushgit hook that captures sessions at commit time - an orphan branch
rekal/<their-email>used to transport memory over git - the full recall skill under
.claude/skills/rekal/ - one marker-tagged line in
CLAUDE.md, plus the equivalent line in any other agent rules file it detects (AGENTS.md,GEMINI.md,.github/copilot-instructions.md,.kiro/steering/rekal.md)
User content is never rewritten — only the marker line is added. rekal clean
removes everything, with no residue.
If the user declines, stop and say so plainly.
Run it
From the repository root:
rekal init
After
Say what to expect, because the first impression is misleading:
- A fresh store is empty. Recall stays silent until the next commit. That silence is correct, not a broken install — memory accumulates from here.
- If the team already shares a ledger,
rekal syncpulls it now and recall has something to find immediately.
From this point the binary owns memory. It installed the full recall skill, which is the one that answers questions — richer than anything in this plugin, and versioned with the binary whose commands it runs. Route recall questions there. This skill is done until the next repository.
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 · 61 lines · 75 tokens per session scan A a0f6700ecef9
init is a skill published in the GitHub repository rekal-dev/rekal-cli (207 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 550 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
memex-sync
Sync Zettelkasten cards across devices via git.
unforgit-memory
Use Unforgit MCP tools as durable repository memory for decisions, conventions, gotchas, and playbooks.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
prepare-pr
Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.