Borrowing it
Nothing to install: this file belongs to niclejeune/pi-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/skills/context-vault/SKILL.mdgit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/context-vault)<a href="https://agentmods.dev/skills/niclejeune/pi-agents-config/context-vault"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/context-vault/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/niclejeune/pi-agents-config/context-vault"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/context-vault.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.00398 |
| Opus 5 | $0.00017 | $0.00199 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
context-vault 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 10d 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
context-vault Skill
Use a context vault for durable memory that should survive beyond one agent session.
Recommended starter: https://github.com/niclejeune/second-brain-starter
Default placeholder path:
~/second-brain
Replace this with your actual vault path in your private config. Do not publish a config that contains private paths, project names, emails, secrets, or client details.
When to use
Use the vault when the task involves:
- persistent memory
- workflow decisions
- self-improvement notes
- project context packs
- architecture decisions
- SOPs / repeatable workflows
- cross-session handoffs
Do not dump noisy logs or full transcripts into compiled wiki pages. Store raw evidence separately and write distilled summaries.
Required first reads
When using a vault, read:
~/second-brain/AGENTS.md
~/second-brain/context-packs/default.md
Adjust paths for your setup.
Suggested vault layout
second-brain/
AGENTS.md
README.md
context-packs/
default.md
wiki/
index.md
log.md
hot-cache.md
decisions/
operations/
projects/
self-improvement/
raw/
tool-logs/
Context hygiene
Persist distilled knowledge, not noisy logs.
Good vault entries:
- decisions and rationale
- stable project facts
- recurring agent mistakes
- setup commands that worked
- validated workflow SOPs
Bad vault entries:
- raw terminal spam in wiki pages
- transient stack traces without summary
- secrets or tokens
- private client data in public templates
- copied session transcripts without curation
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.
- 10d ago First seen · 84 lines · 35 tokens per session scan A 7a1f4461c911
context-vault is a skill published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 398 once invoked, about $0.0002 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 skills, from other repositories
reflect
Capture reusable session learnings. Use when updating agent instructions, adding lessons learned, preserving project conventions, or fixing repeated mistakes.
brain-page
Operating manual for reading and writing a project's brain — every read and write goes through the bundled zero-dependency brain CLI; never hand-edit brain files. Read it before creating or modifying any page or root page.
brain-setup
Bootstrap the Open Project Brain Standard into the current project — prefer brain init (ensure BRAIN.md, scaffold empty brain brainRoot-aware, default-wire CLAUDE.md + AGENTS.md). Optionally install a pre-commit hook and a Claude Code or Codex SessionStart hook.
brain-bootstrap
Seed a freshly-scaffolded brain with real project knowledge — on an existing (brownfield) project read the code, docs, and git log to draft the six root pages and capture key historical decisions; on a near-empty (greenfield) project interview the user. Every write goes through the brain CLI. Run it after brain-setup.
brain-ingest
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.
immune
Hybrid adaptive memory: Cheatsheet (positive patterns pre-generation) and Immune (negative patterns post-generation) with Hot/Cold tiered auto-learning. Triggers on: "scan for errors", "immune scan", "check output quality", "antibody scan". NOT for PR review (use pr-review) or repo audits (use repo-sentinel).