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/infohata/mind-vault/agents-mdgit clone --depth 1 https://github.com/infohata/mind-vaultWrote 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/infohata/mind-vault/agents-md)<a href="https://agentmods.dev/instructions/infohata/mind-vault/agents-md"><img src="https://agentmods.dev/badge/instructions/infohata/mind-vault/agents-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.03114 | $0.03114 |
| Opus 5 | $0.01557 | $0.01557 |
| Sonnet 5 | $0.00623 | $0.00623 |
| Haiku 4.5 | $0.00311 | $0.00311 |
Grade A, and why
mind-vault AGENTS.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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Coding Guidelines for mind-vault
This guide is for agentic coding assistants (Claude Code, OpenCode) working in this repository.
Project Overview
mind-vault is a centralized configuration, skills, and rules repository for AI agents. It contains:
- skills/ - Reusable agent skills (SKILL.md files)
- agents/ - Custom agent definitions (AGENT.md files)
- rules/ - Shared behavioral rules (RULE.md files)
- docs/ - Analysis and pattern documentation
- .claude-plugin/ - Claude Code plugin manifests (additive CC install channel; see below)
This is not a typical application - there are no tests, build steps, or runtime execution. Focus is on clarity, completeness, and reusability.
Distribution — two channels. mind-vault installs into agent hosts via per-host symlink scripts (scripts/setup-*-symlinks.sh) or, on Claude Code only, as a native plugin (/plugin marketplace add infohata/mind-vault → /plugin install mv@mind-vault). The two coexist but pick one per machine (both = double-load). On the plugin channel, commands/ entries namespace under mv: (type /mv:wrap), while skill triggers are unaffected (description-invoked). rules/, docs/rules/, and the statusline stay script-wired on both channels.
Commands & Workflow
Git Workflow
CRITICAL: All git operations follow rules/RULE_git-safety.md
Key requirements:
- Work on feature branches only (never commit to
mainor the release branch) - Commit freely on feature branches — the PR is the human review gate, not each commit
- Never merge into
mainor the release branch — the human merges on GitHub - Use
--force-with-lease(never plain--force); never bypass hooks with--no-verify
See rules/RULE_git-safety.md for full details.
No Build/Test/Lint Steps
- This project has no Makefile, pytest, linting, or build pipeline
- There are no tests to run (it's a configuration repository)
- No installation dependencies or virtual environments needed
- Validation happens through code review and documentation clarity
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.
- 4d ago First seen · 393 lines · 3,114 tokens per session scan A 241e5a8d621d
mind-vault AGENTS.md is an instructions file published in the GitHub repository infohata/mind-vault (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,114 tokens to every session, about $0.0156 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.