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/mpazik/BinderWrote 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/mpazik/binder/journal)<a href="https://agentmods.dev/plugins/mpazik/binder/journal"><img src="https://agentmods.dev/badge/plugins/mpazik/binder/journal/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/mpazik/binder/journal"><img src="https://agentmods.dev/badge/plugins/mpazik/binder/journal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
journal 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": "journal",
"description": "Personal journaling system built on Binder — morning briefings, day planning, reflections, summaries, and period-level goal tracking.",
"version": "0.1.0",
"author": {
"name": "Binder"
}
}
What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 148 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.
- 1mo ago First seen · 9 lines scan A 0bd2a474b395
journal is a plugin published in the GitHub repository mpazik/Binder (40 stars, last pushed 25d 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-30.
Other plugins, from other repositories
anytype-toolbox-skills
Agent Skills for Anytype setup, including a dedicated headless account for one LLM-sharing space, plus anyr and any-mcp workflows.
engraphis-memory
Give agents durable, scoped, explainable memory across sessions and repos via the Engraphis MCP tools. Use when you learn something worth keeping, need prior context before acting, or ask why/how a fact changed. Covers remember/recall, why/timeline, forget/pin/correct, sessions, and code search.
7xuanlu-wenlan marketplace
Plugin marketplace listing 1 plugin: wenlan.
graft
Persistent local memory for coding agents: recall past fixes, decisions and gotchas before solving them again, and save what was learned.
unforgit-claude-code-marketplace
Claude Code plugins for Unforgit persistent repository memory.
unforgit
Persistent repository memory for AI coding agents using MCP tools, repository rules, and durable project knowledge.