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.
git clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/plugins/mtarcure/claude-vibe-squad/chrono-vault)<a href="https://agentmods.dev/plugins/mtarcure/claude-vibe-squad/chrono-vault"><img src="https://agentmods.dev/badge/plugins/mtarcure/claude-vibe-squad/chrono-vault.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
chrono-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 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.
What it actually says
{
"name": "chrono-vault",
"version": "0.1.0",
"description": "Chrono squad memory: private off-repo markdown source of truth with disposable FTS5/BM25 recall, fail-closed root resolution, and per-lane sensitivity clearance.",
"license": "AGPL-3.0-or-later",
"mcpServers": {
"chrono-vault": {
"command": "${CLAUDE_PLUGIN_ROOT}/../../.venv/bin/python",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp_server.py"],
"env": {
"OBSIDIAN_REST_API_KEY": "${OBSIDIAN_REST_API_KEY}",
"OBSIDIAN_VAULT_ROOT": "${OBSIDIAN_VAULT_ROOT}",
"CHRONO_VAULT_ROOT": "${CHRONO_VAULT_ROOT}"
}
},
"chrono-kg": {
"command": "${CLAUDE_PLUGIN_ROOT}/../../.venv/bin/python",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp_server.py", "--namespace", "kg"],
"env": {
"OBSIDIAN_REST_API_KEY": "${OBSIDIAN_REST_API_KEY}",
"OBSIDIAN_VAULT_ROOT": "${OBSIDIAN_VAULT_ROOT}",
"CHRONO_VAULT_ROOT": "${CHRONO_VAULT_ROOT}"
}
},
"chrono-obsidian": {
"command": "${CLAUDE_PLUGIN_ROOT}/../../.venv/bin/python",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp_server.py", "--namespace", "obsidian"],
"env": {
"OBSIDIAN_REST_API_KEY": "${OBSIDIAN_REST_API_KEY}",
"OBSIDIAN_VAULT_ROOT": "${OBSIDIAN_VAULT_ROOT}",
"CHRONO_VAULT_ROOT": "${CHRONO_VAULT_ROOT}"
}
}
}
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 182 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 36 lines scan A 05d6bdb3ab39
chrono-vault is a plugin published in the GitHub repository mtarcure/claude-vibe-squad (90 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
openrig-core
OpenRig canonical skills and hooks for cross-runtime agent topology coordination, continuity, and operating discipline.
personal
Personal knowledge and finance automation — autonomous Obsidian vault management (PARA + LLM Wiki) and end-to-end corporate/personal tax preparation from Xero, bank statements, and Google Drive.
sessions
Skills for summarizing and recalling AI coding sessions across Claude Code, Codex, Pi, and OpenCode.
unforgit-claude-code-marketplace
Claude Code plugins for Unforgit persistent repository memory.
context-guard
Context-budget guard for long Claude Code sessions: a Stop hook enforces a per-model checkpoint protocol (mechanical stub + budgeted memory-writer subagent), and a SubagentStop tracker surfaces true session spend (main thread + subagents). Default protocol uses only vanilla Claude Code; a scoped memory layer is…
logs-locally-plugin
Store and browse AI agent session logs locally with a SQLite database and web UI.