agentmods.dev

rekal-cli: Instructions file for Claude Code

CLAUDE.md

rekal-cli CLAUDE.md is an instructions file for Claude Code from rekal-dev/rekal-cli. It costs 16,727 tokens per session, scanned B, original, Apache-2.0.

A set of Claude Code instructions for Rekal CLI, a single-binary command-line tool with built-in storage, search, memory, and compression components.

In plain words
What is it for?
It helps with design decisions, problem investigation, command changes, package changes, documentation updates, and maintenance of the CLI's architecture.
Why use it?
It tells the agent to consult Rekal's guiding rules and existing memories before making decisions, while keeping commands and documentation consistent.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is rekal-dev/rekal-cli's own configuration. It tells Claude Code how to work on rekal-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything rekal-cli configures →

not rated 205repo +2 changed 1mo ago B scan 16,727 tokens original Apache-2.0
View source ↗ rekal-dev/rekal-cli rekal.dev
Reuse

Borrowing it

Nothing to install: this file belongs to rekal-dev/rekal-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rekal-dev/rekal-cli/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/rekal-dev/rekal-cli

Made for: Claude Code.

Wrote 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.

agentmods badge for rekal-cli CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rekal-dev/rekal-cli/claude-md/github.svg)](https://agentmods.dev/instructions/rekal-dev/rekal-cli/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/rekal-dev/rekal-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/rekal-dev/rekal-cli/claude-md/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.

agentmods 80×15 button for rekal-cli CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rekal-dev/rekal-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/rekal-dev/rekal-cli/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16,727 This file is loaded in full into every session.
When invoked 16,727 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.16727 $0.16727
Opus 5.5 $0.06691 $0.06691
Sonnet 5.5 $0.03345 $0.03345
Haiku 4.5 $0.01673 $0.01673

Measured 1mo ago against content hash be719a49e534, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

rekal-cli CLAUDE.md scanned grade B 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 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.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

dir (`.claude/skills/<name>/.rekal-version`); `maybeRefreshStaleSkill` (called
CLAUDE.md · 1,000 lines

How it starts

The opening of the file, as written. The whole thing — 1,000 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rekal CLI

Soul

Before making any design decision, read SOUL.md. It defines the two problems Rekal exists to solve and the seven beliefs that guide every choice. If a decision conflicts with the soul, the decision is wrong.

When working on a problem, consult Rekal's own memories first:

rekal "<describe the problem>"

The prior context for what you're working on may already exist.

Standing Rules

  • Keep this file up to date. Any change to commands, packages, files, or behavior must be reflected here. Update --help text when command behavior changes. Update docs/spec/command/ when a command spec changes. Stale docs are worse than no docs.
  • Consult SOUL.md before design decisions. Consult rekal before starting work on a problem.

Architecture

Single binary. Everything embedded — CLI, database engine, embedding model, compression dictionary.

  • CLI: Cobra (github.com/spf13/cobra)
  • Storage: DuckDB via github.com/marcboeker/go-duckdb (database/sql interface)
  • Compression: zstd via github.com/klauspost/compress with preset dictionary
  • IDs: ULID via github.com/oklog/ulid/v2
  • Embeddings: LSA (gonum) + Nomic (platform-specific builds)
  • Build: mise, go modules
  • Lint: golangci-lint v2 (2.8.0)
  • Language: Go 1.25.6

Two databases in .rekal/:

  • data.db — immutable source of truth. Append-only. Pushed to git.
  • index.db — local derived index. Rebuilt from data.db. Never pushed.

This split is a direct consequence of the soul: thin on the wire, rich on the machine.

The .rekal/ store lives in the repository's main worktree; every linked git worktree resolves to that one shared store via gitx.MainWorktreeRoot (a no-op for non-worktree repos, so existing installs need no migration). All store-path helpers (db.StoreDir, cli.RekalDir, and the Open*/*Path functions) funnel through it; git-state helpers (HeadSHA/CurrentBranch) and session discovery keep using the invoking worktree. The no-op is enforced by identity, not by string: git reports worktree paths with symlinks resolved, so a repo reached through a symlinked directory (macOS /var → /private/var, or any symlinked project dir) would otherwise come back under a different name for the same place and move .rekal/ off the store that already exists — preferCallerPath stats both and hands the caller's own spelling back.

Read the full file on GitHub · 1,000 lines

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. 1mo ago Changed · +4 lines · +77 tokens per session be719a49e534
  2. 1mo ago First seen · 996 lines · 16,650 tokens per session scan B a3dfa5423ffb

Subscribe to this mod's changes

rekal-cli CLAUDE.md is an instructions file published in the GitHub repository rekal-dev/rekal-cli (205 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16,727 tokens to every session, about $0.0669 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude CodeMemory and contextagent-memoryai-codingclicode-contextdeveloper-tools
Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

vscode model-prompts.instructions.md

Model-specific prompt authoring and registry guidelines.

microsoft/vscode · 2,022 tokens