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.
/plugin marketplace add Dhevenddra/forensic-deepdivenpx agentmods add plugins/dhevenddra/forensic-deepdive/v0_8_0git clone --depth 1 https://github.com/Dhevenddra/forensic-deepdiveWrote 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/dhevenddra/forensic-deepdive/v0_8_0)<a href="https://agentmods.dev/plugins/dhevenddra/forensic-deepdive/v0_8_0"><img src="https://agentmods.dev/badge/plugins/dhevenddra/forensic-deepdive/v0_8_0.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
forensic-deepdive-codebase 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 3d 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": "forensic-deepdive-codebase",
"version": "0.2.0",
"description": "Forensic codebase brief for surface_v0_8_0 \u2014 five markdown artifacts (MAP, HOTPATHS, ARCHAEOLOGY, MENTAL_MODEL, AGENT_BRIEF) plus five single-intent Claude skills covering exploring / debugging / impact-analysis / refactoring / onboarding workflows.",
"author": {
"name": "forensic-deepdive"
},
"keywords": [
"codebase",
"onboarding",
"knowledge-graph",
"code-review"
],
"skills": [
{
"name": "codebase-exploring",
"path": ".claude/skills/codebase-exploring/SKILL.md"
},
{
"name": "codebase-debugging",
"path": ".claude/skills/codebase-debugging/SKILL.md"
},
{
"name": "codebase-impact-analysis",
"path": ".claude/skills/codebase-impact-analysis/SKILL.md"
},
{
"name": "codebase-refactoring",
"path": ".claude/skills/codebase-refactoring/SKILL.md"
},
{
"name": "codebase-onboarding",
"path": ".claude/skills/codebase-onboarding/SKILL.md"
}
]
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 614 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.
- 3d ago First seen · 37 lines scan A 0ee8da812e5c
forensic-deepdive-codebase is a plugin published in the GitHub repository Dhevenddra/forensic-deepdive (2 stars, last pushed 18d 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-31.
Other plugins, from other repositories
engram
The context spine that 10x's your Claude Code sessions. Local-first SQLite knowledge graph + MCP server that intercepts file reads and replaces them with structural summaries. Measured 89% token reduction on a real codebase. Apache 2.0, no cloud, no telemetry.
superlocalmemory-codex
Local-first agent memory with auditable hybrid retrieval — the Codex build, with Codex-shaped rules, hooks and launcher.
nexus-memory
Persistent memory for Claude Code via Qdrant. Auto-Recall injects relevant memories before each prompt. Auto-Capture stores facts after each turn. Self-hosted, private, universal.
yaggo-brain
yaggo-brain panel integration for Claude Code.
agent-recall
Persistent memory for AI coding agents. SQLite knowledge graph with scoped entities, MCP tools, and LLM-summarized briefings.
symbiote
AI coding companion with persistent memory — code knowledge graph, developer DNA, and architectural intelligence via MCP.