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/HelloRuru/claude-memory-engineWrote 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/commands/helloruru/claude-memory-engine/diary)<a href="https://agentmods.dev/commands/helloruru/claude-memory-engine/diary"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/diary/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/commands/helloruru/claude-memory-engine/diary"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/diary.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.00000 | $0.00206 |
| Opus 5.5 | $0.00000 | $0.00082 |
| Sonnet 5.5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
diary 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
/diary -- Session Reflection Diary
Generate a reflection diary entry from the current conversation.
Steps
- Review this conversation: List the user's main requests, problems solved, and files modified
- Write a diary entry: Save to
~/.claude/sessions/diary/with date-based filename - Format:
# Diary {YYYY-MM-DD}
## What I did today
- {List main work items}
## What I learned
- {Pitfalls, discoveries, user preferences}
## Patterns I noticed
- {User's work patterns, recurring needs}
## Notes for next time
- {Reminders for future sessions}
- Report: Briefly say "Diary written, noted X key points"
Notes
- Keep it concise and actionable, not a verbose log
- Focus on "what I learned" and "patterns", not play-by-play
- Each entry should be under 30 lines
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 · 33 lines · 0 tokens per session scan A 1b1622b34223
diary is a command published in the GitHub repository HelloRuru/claude-memory-engine (134 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 206 tokens. 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 commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
golden-path
The golden path. One command, idea to merged PR. Runs the full pipeline, prd → prp → plan → dev → test → pr, with sensor + eval gates at every stage.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.