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/phense/agentic-ragWrote 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/phense/agentic-rag/claude)<a href="https://agentmods.dev/plugins/phense/agentic-rag/claude"><img src="https://agentmods.dev/badge/plugins/phense/agentic-rag/claude/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/phense/agentic-rag/claude"><img src="https://agentmods.dev/badge/plugins/phense/agentic-rag/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agentic-rag 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 yesterday.
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
{
"description": "Source-backed knowledge, durable compaction handoffs and bounded queued tools.",
"hooks": "./hooks/hooks.json",
"mcpServers": "./.mcp.json",
"name": "agentic-rag",
"version": "0.6.12"
}
What it installs
The manifest is a name and a version. 6 hooks, 1 MCP server travel with it, and installing the plugin installs all of 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.
- yesterday First seen · 8 lines scan A 7a3a58f36f52
agentic-rag is a plugin published in the GitHub repository phense/agentic-rag (0 stars, last pushed yesterday), 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-30.
Other plugins, from other repositories
context-canopy
Portable personal AI context: search and capture knowledge, then read allowlisted user authority across agents.
keymem
Associative long-term memory — recall by key-graph association, plus passive memory surfacing on every prompt.
core-memory-kit
Per-project in-repo memory system for Claude Code. Frozen-snapshot session loads, auto-extract Stop hook, memory-write + memory-search + troubleshooting skills, keyword search, optional auto-curation crons.
milepost
Milestone-triggered, in-session work diary for Claude Code. The model records meaningful milestones to plain-markdown log + status files as it works, across all projects. No database.
ultramemory-kit
UltraMemory Agent Kit — recall-first memory (Turbo Token Saver), the grounding/checklist harness, and optional MCP + Playwright setup for Claude Code. Bring your own UltraMemory API key.
claude-recap
Topic-based automatic memory for Claude Code — never lose context across sessions or compactions.