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 agentmods add instructions/janbjorge/rekal/claude-mdgit clone --depth 1 https://github.com/janbjorge/rekalWrote 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/instructions/janbjorge/rekal/claude-md)<a href="https://agentmods.dev/instructions/janbjorge/rekal/claude-md"><img src="https://agentmods.dev/badge/instructions/janbjorge/rekal/claude-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00220 | $0.00220 |
| Opus 5 | $0.00110 | $0.00110 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
rekal CLAUDE.md 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 5d 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
Read AGENTS.md before doing anything.
Pre-commit workflow (required before every commit and push)
Run all four CI checks locally and fix anything they flag. Don't push until they all pass. CI runs the same checks and will reject otherwise.
uv run ruff check rekal/ tests/
uv run ruff format rekal/ tests/
uv run ty check rekal/ tests/
uv run pytest --cov=rekal --cov-report=term-missing --cov-fail-under=100 tests/
Notes:
- Use
ruff format(not--check) so formatting fixes are applied in-place before staging. - If
ty checkreports new errors, fix the types. Do not silence with# type: ignoreunless the error is a known tool limitation. - If coverage drops below 100%, add tests rather than
# pragma: no cover. - Run these after every meaningful edit, not just at the end. Catching a format/lint error early avoids a fixup commit later.
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.
- 5d ago First seen · 23 lines · 220 tokens per session scan A 6ec6346aabff
rekal CLAUDE.md is an instructions file published in the GitHub repository janbjorge/rekal (53 stars, last pushed 10d ago), licensed MIT. It adds 220 tokens to every session, about $0.0011 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.
Other instructions, from other repositories
Vault-Agent-Memory AGENTS.md
Instructions for zycaskevin/Vault-Agent-Memory, covering agent instructions for vault agent memory, common install architecture, second decision: optional features, first decision: database scope and safe agent workflow.
swag-mcp CLAUDE.md
Claude Code instructions for jmagar/swag-mcp, covering swag mcp - claude memory reference, project overview, core architecture, key components and common development commands.
state-memory-mcp copilot-instructions.md
Instructions for putervision/state-memory-mcp, covering state memory (state-memory-mcp), 1. priority order, 2. when to write to the graph, 3. workflow pattern and 4. codebase seeding on initialization.
personal-notes-assistant CLAUDE.md
Instructions for coeusyk/personal-notes-assistant, covering personal-notes-assistant, architecture, adding a tool, milvus notes (non-obvious, bit people twice already) and running / testing locally.
Mycorrhiza-MCP CLAUDE.md
Instructions for sfaustodev/Mycorrhiza-MCP, covering claude.md, what this is, commands, or, after install and architecture.
post-cortex CLAUDE.md
Instructions for julymetodiev/post-cortex, covering claude.md, session, rules, interaction types and mcp tools.