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/pax-beehive/paxmWrote 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/pax-beehive/paxm/paxm-claude)<a href="https://agentmods.dev/plugins/pax-beehive/paxm/paxm-claude"><img src="https://agentmods.dev/badge/plugins/pax-beehive/paxm/paxm-claude.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
paxm-claude 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 8d 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":"paxm-claude","version":"0.1.18","description":"Passive and active paxm memory for Claude Code","author":{"name":"PAX"}}
What it installs
The manifest is a name and a version. 2 skills, 5 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 29 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.
- 8d ago First seen · 2 lines scan A 84dcc7067ada
paxm-claude is a plugin published in the GitHub repository pax-beehive/paxm (421 stars, last pushed 10d ago), licensed Apache-2.0. 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-08-30.
Other plugins, from other repositories
plur
Persistent, local-first shared memory for AI agents. Corrections, preferences, and conventions persist across sessions, tools, and machines — stored as plain YAML on your disk, with zero-cost local search.
engraphis-memory
Give agents durable, scoped, explainable memory across sessions and repos via the Engraphis MCP tools. Use when you learn something worth keeping, need prior context before acting, or ask why/how a fact changed. Covers remember/recall, why/timeline, forget/pin/correct, sessions, and code search.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
superlocalmemory-codex
Local-first agent memory with auditable hybrid retrieval — the Codex build, with Codex-shaped rules, hooks and launcher.
talamus-memory
Durable, local-first agent memory with cited retrieval, provenance, history, and MCP tools.
talamus
Local-first, source-grounded memory for Gemini CLI and other AI agents.