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 jongwony/epistemic-protocolsnpx agentmods add plugins/jongwony/epistemic-protocols/anagogegit clone --depth 1 https://github.com/jongwony/epistemic-protocolsWrote 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/jongwony/epistemic-protocols/anagoge)<a href="https://agentmods.dev/plugins/jongwony/epistemic-protocols/anagoge"><img src="https://agentmods.dev/badge/plugins/jongwony/epistemic-protocols/anagoge.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
anagoge 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 today.
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": "anagoge",
"description": "Elevate a vague recall to a higher-granularity unit — /ascend (ἀναγωγή: a leading-up)",
"version": "1.0.4",
"author": {
"name": "Jongwon Choi",
"url": "https://github.com/jongwony"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 45 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.
- today Changed 08592e84ca15
- 4d ago First seen · 10 lines scan A 13d818cbac0e
anagoge is a plugin published in the GitHub repository jongwony/epistemic-protocols (160 stars, last pushed today), 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-30.
Other plugins, from other repositories
archcore
Spec-driven development and context engineering for AI coding agents, backed by project context in Git.
recall
Cross-session, cross-project conversation recall with SQLite storage, auto-tagging, compaction recovery, highlight sharing, and proactive recall assistant skill.
yaps-memory
Persistent private memory for Claude, stored as local Markdown.
hydradb
Secure HydraDB automation for Claude Code with workspace sync, prompt recall, and conversation capture.
productivity
Manage tasks, plan your day, and build up memory of important context about your work. Syncs with your calendar, email, and chat to keep everything organized and on track.
usemycontext
Your personal context, served to Claude Code over MCP. Map each folder to one of your @handle profiles so every session in that folder reads the right context.