Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yuki4266/life-log/plugin install 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/skills/yuki4266/life-log/setup)<a href="https://agentmods.dev/skills/yuki4266/life-log/setup"><img src="https://agentmods.dev/badge/skills/yuki4266/life-log/setup/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/skills/yuki4266/life-log/setup"><img src="https://agentmods.dev/badge/skills/yuki4266/life-log/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00105 | $0.00419 |
| Opus 5.5 | $0.00042 | $0.00168 |
| Sonnet 5.5 | $0.00021 | $0.00084 |
| Haiku 4.5 | $0.00011 | $0.00042 |
Grade A, and why
setup 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
Life-log setup
Scaffold the current folder into a life-log project by running the bundled,
idempotent scaffold script. It creates the .life-log marker, the 8 category
files, a CLAUDE.md with the always-on recording rules, and a starter README —
and it never overwrites files that already exist, so it's safe to re-run.
Steps
- Run the scaffold script:
Ifbash "${CLAUDE_PLUGIN_ROOT}/skills/setup/scaffold.sh"$CLAUDE_PLUGIN_ROOTisn't set in the shell, find this skill's directory (it holds thisSKILL.md) and runscaffold.shfrom there. - Read the script's output and tell the user exactly what was created (or that the folder was already set up).
- Show them how to start — for example:
Done! Your life log is ready. Just talk to me — try:
- "ran 5k this morning" → filed to health.md
- "had a rough day at work" → filed to work.md + mood.md
Every message you send here gets classified, timestamped, and saved. Nothing is ever lost.
After setup, the recording rules in the new CLAUDE.md take over automatically —
see the log skill for the recording behavior itself.
What ships with it
1 file beside SKILL.md 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 · 34 lines · 105 tokens per session scan A da159b426471
setup is a skill published in the GitHub repository yuki4266/life-log (1 stars, last pushed 3mo ago), licensed MIT. It adds 105 tokens to every session and 419 once invoked, about $0.0004 per session on Opus 5.5. 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 skills, from other repositories
create-kr-patch
Use for Korean (Hangul) fan translations of retro console or PC games, including ROM or disc analysis, text-engine reverse engineering, Hangul fonts and custom encodings, script extraction and reinsertion, code hooks, reproducible product builds, and emulator verification. Apply it to new investigations and follow-up…
yolo-brief
Use to record a new feature in a YOLO repo, or to cancel one. Writes workspace/features/ /brief.md with a goal and checkable success criteria, taken from an approved design spec when one exists. Triggers on "track this as a feature", "write a brief for X", "track it from that spec", "yolo brief", "cancel the X…
0xarchive
Query historical and real-time crypto market data from 0xArchive across two venues: Hyperliquid and Lighter. Lighter has two deployments: mainnet at /v1/lighter and Robinhood Chain at /v1/rh-lighter (USDG-quoted, e.g. BTC, AAPL-USDG). Hyperliquid includes HIP-3 builder perps (/v1/hyperliquid/hip3), HIP-4 outcome…
liquid-glass
Builds, reviews, and migrates SwiftUI interfaces that use Apple's Liquid Glass design on iOS, iPadOS, macOS, watchOS, and tvOS 26 and 27. Covers glassEffect and the Glass variants, GlassEffectContainer and morphing, the glass button styles, concentric shapes, the system glass chrome (toolbars, tab bars, search…
slopmop
Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to sm swab, sm scour, sm buff, sm sail, sm refit, or sm doctor so remediation follows the established rails. Also trigger when asked to "install" or "set up" slop-mop in a repo, or when you find a repo with sm…
cpp-mentor
A general, self-adapting C++ mentor for any project. On first run with an empty profile it onboards: settles the goal and domain, derives a namespace from the goal, agrees conventions including the project's own error policy, and audits the developer's level in both C++ and the project's topic — with questions…