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/mhashim6/kauriWrote 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/mhashim6/kauri/marketplace)<a href="https://agentmods.dev/plugins/mhashim6/kauri/marketplace"><img src="https://agentmods.dev/badge/plugins/mhashim6/kauri/marketplace/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/mhashim6/kauri/marketplace"><img src="https://agentmods.dev/badge/plugins/mhashim6/kauri/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kauri marketplace 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 1mo 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": "kauri",
"owner": {
"name": "mhashim6"
},
"plugins": [
{
"name": "kauri",
"source": {
"source": "git-subdir",
"url": "mhashim6/kauri",
"path": "plugins/claude-code"
},
"description": "Deterministic decision records for agents and humans — hooks, skills, and 12 MCP tools",
"version": "0.1.2"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 1mo ago First seen · 19 lines scan A 54455b49a0a8
kauri marketplace is a plugin published in the GitHub repository mhashim6/kauri (5 stars, last pushed 5mo 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-08-31.
Other plugins, from other repositories
memX
memX: local-first semantic memory for coding agents. Native Claude Code lifecycle hooks.
tsubasa
Captain persona: repo-resident domain expert with a git-stored knowledge graph, ambient knowledge capture, and ADR-threaded delegation.
agmem
Persistent project memory for Claude Code — indexes your repo into local JSONL and auto-injects task-relevant context (BM25, no LLM calls, nothing leaves your machine).
claude-md-management
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
deja
deja-vu memory for Gemini CLI: the coding sessions already on your disk — Gemini CLI, Claude Code, Codex, Cursor and thirty-eight more — searchable and recalled, including work from before it was installed.
causal-memory
Persistent causal memory for Claude Code — decisions, outcomes, and lessons that survive compaction. Same-context counterfactuals (natural experiments), a falsifiable prediction ledger, and an activation skill that teaches when to recall and record.