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/abm9111/chamberWrote 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/abm9111/chamber/plugin)<a href="https://agentmods.dev/plugins/abm9111/chamber/plugin"><img src="https://agentmods.dev/badge/plugins/abm9111/chamber/plugin/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/plugins/abm9111/chamber/plugin"><img src="https://agentmods.dev/badge/plugins/abm9111/chamber/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chamber 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 2d 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": "chamber",
"description": "Checks that the numbers, capitalised names, and file names in a claim occur in the indexed note. Local, no model. It does not judge meaning.",
"version": "0.2.2",
"author": {
"name": "abm9111",
"url": "https://github.com/abm9111"
},
"homepage": "https://github.com/abm9111/chamber#readme",
"repository": "https://github.com/abm9111/chamber",
"license": "MIT",
"keywords": [
"mcp",
"notes",
"obsidian",
"citations",
"grounding",
"verification",
"local-first"
],
"userConfig": {
"notes": {
"type": "directory",
"title": "Notes folder",
"description": "The folder of notes Chamber checks claims against, such as your Obsidian vault.",
"required": true
},
"exclude": {
"type": "string",
"title": "Folders to skip",
"description": "Names or patterns to leave out, such as .obsidian or *sync-conflict*. A name cannot contain a comma.",
"multiple": true,
"required": false
}
},
"mcpServers": {
"chamber": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/launch.mjs",
"@bu7umaid/[email protected]",
"--notes",
"${user_config.notes}",
"--exclude",
"${user_config.exclude}"
]
}
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 70 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 50 lines scan A 0686f81e4d5a
chamber is a plugin published in the GitHub repository abm9111/chamber (3 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-10-26.
Other plugins, from other repositories
remember
Extended Second Brain that learns as you work in Claude Code.
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP. STDIO or Streamable HTTP.
mcp
Read, write, search, and manage your Kept conversation vault.
sync
Sync: Claude and Codex council orchestration. Routes work by role across declared pools, requires current headroom before any capacity claim, coordinates through run directories, gates on executed commands, and evolves policy from recorded outcomes.
Notebooklab Claude Outcome Bundle
Public-ready Claude Code starter bundle for Notebooklab MCP outcome workflows.
obsidian-chronicle
Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with…