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/TheWinci/mimirsWrote 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/thewinci/mimirs/marketplace)<a href="https://agentmods.dev/plugins/thewinci/mimirs/marketplace"><img src="https://agentmods.dev/badge/plugins/thewinci/mimirs/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/thewinci/mimirs/marketplace"><img src="https://agentmods.dev/badge/plugins/thewinci/mimirs/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mimirs 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": "mimirs",
"owner": {
"name": "TheWinci",
"url": "https://github.com/TheWinci"
},
"plugins": [
{
"name": "mimirs",
"source": {
"source": "github",
"repo": "TheWinci/mimirs"
},
"description": "Persistent project memory for AI coding agents — semantic search, AST-aware chunking, dependency graphs, conversation history, annotations, and wiki generation"
}
]
}
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 ships with it
1 file beside marketplace.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.
- 1mo ago First seen · 18 lines scan A 6a693ec279f4
mimirs marketplace is a plugin published in the GitHub repository TheWinci/mimirs (30 stars, last pushed yesterday), 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
repobrain
Repository knowledge engine plugin. Bundles CLI-backed slash commands (rb-setup / rb-init / rb-refresh / rb-ask) plus the agent-repo-init skill. Works in both Claude Code and Codex CLI.
memorix
Shared workspace memory for Claude Code and other AI coding agents.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
synapse-mcp
Persistent AST knowledge graph and safe writes for AI coding agents across 50+ languages. 100% local — no cloud indexing, no telemetry.
obsidian-wiki
Grow an Obsidian second brain with your AI agent: ingest docs, chat history and URLs into interlinked markdown, then query it with citations. Karpathy's LLM Wiki pattern as Claude Code skills.
project-brain
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.