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/yuki4266/life-logWrote 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/yuki4266/life-log/life-log)<a href="https://agentmods.dev/plugins/yuki4266/life-log/life-log"><img src="https://agentmods.dev/badge/plugins/yuki4266/life-log/life-log/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/yuki4266/life-log/life-log"><img src="https://agentmods.dev/badge/plugins/yuki4266/life-log/life-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
life-log 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": "life-log",
"description": "Talk to Claude Code like a friend — a complaint or a quick note — and it auto-classifies, timestamps, and files each message into dated category notes, then gives you a suggestion. A UserPromptSubmit safety-net hook means nothing you say is ever lost. Local-first, plain markdown, no cloud.",
"version": "0.1.0",
"author": {
"name": "yuki4266",
"url": "https://github.com/yuki4266"
},
"homepage": "https://github.com/yuki4266/life-log",
"repository": "https://github.com/yuki4266/life-log",
"license": "MIT",
"keywords": [
"journaling",
"life-log",
"diary",
"productivity",
"local-first",
"markdown",
"companion"
]
}
What it installs
The manifest is a name and a version. 3 skills, 1 hook travel with it, and installing the plugin installs all of them — 300 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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 · 22 lines scan A 2d4008fb016b
life-log is a plugin published in the GitHub repository yuki4266/life-log (1 stars, last pushed 3mo 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-31.
Other plugins, from other repositories
obsidian-chronicle
Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with…
7xuanlu-wenlan marketplace
Plugin marketplace listing 1 plugin: wenlan.
claude-code-hermit
Your own local Claude Tag, in the Claude app, Discord, Telegram, or a custom Claude Code channel.
scout
Autonomous knowledge management and daily briefing system. Monitors your work tools (Slack, Calendar, Linear, GitHub, etc.), synthesizes findings into a persistent knowledge base with a formal ontology, and delivers daily action items — all running unattended via scheduled Claude Code sessions. Six session types…
cc-hud
Compact statusline HUD for Claude Code — context, agents, rate limits.
remembrall
Context-aware session continuity for Claude Code — Pensieve session memory, Time-Turner parallel agents, Marauder's Map visualization, autonomous overnight runs, git patch snapshots, team handoffs, smart replay, and auto-resume.