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/villanub/borgmemory/claude-mdgit clone --depth 1 https://github.com/villanub/borgmemoryWrote 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/villanub/borgmemory/claude-md)<a href="https://agentmods.dev/instructions/villanub/borgmemory/claude-md"><img src="https://agentmods.dev/badge/instructions/villanub/borgmemory/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.00304 | $0.00304 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
borgmemory 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 3d 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
CLAUDE.md — Project Borg
Borg Namespace
For this repository, use Borg namespace borg.
Always pass namespace="borg" to:
borg_thinkborg_learnborg_recall
Do not omit the namespace.
Do not use default for work in this repository.
When to use Borg
borg_think
Call borg_think before complex tasks to retrieve relevant project context, prior decisions, and working patterns.
Use:
- When starting work on a file or module you have not touched in the current session
- When debugging
- When making architecture or design decisions
- When writing docs, proposals, or project explanations
Example:
borg_think(
query="Project Borg repository context, recent decisions, and active development areas",
namespace="borg",
task_hint="architecture",
)
borg_learn
Call borg_learn after significant decisions, discoveries, or non-obvious fixes that should persist across sessions.
Example:
borg_learn(
content="Fixed Borg issue. Root cause was ... Solution was ...",
source="claude-code",
namespace="borg",
)
borg_recall
Call borg_recall for direct searches when you want raw memory rather than compiled context.
Example:
borg_recall(
query="OSS release cleanup",
namespace="borg",
memory_type="semantic",
)
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.
- 3d ago First seen · 64 lines · 304 tokens per session scan A 225d7305bc37
borgmemory CLAUDE.md is an instructions file published in the GitHub repository villanub/borgmemory (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 304 tokens to every session, about $0.0015 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-31.
Other instructions, from other repositories
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
cognirepo CLAUDE.md
Instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).