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.
npx agentmods add commands/rna4219/memx-core/journalgit clone --depth 1 https://github.com/RNA4219/memx-coreWrote 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/rna4219/memx-core/journal)<a href="https://agentmods.dev/commands/rna4219/memx-core/journal"><img src="https://agentmods.dev/badge/commands/rna4219/memx-core/journal.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00198 |
| Opus 5 | $0.00000 | $0.00099 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
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 4d 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
Add Journal Entry
Add a time-series log entry to memx journal store.
Usage
/journal --scope <scope> <log content>
Required Arguments
--scope: Working scope (e.g.,project:memx,session:abc,self)
What it does
- Creates a journal entry with the specified working scope
- Journal entries are time-ordered logs (progress, decisions, events)
- Can be filtered by scope later
Example
/journal --scope project:memx Completed CRUD implementation for journal store
Implementation
Use the Bash tool to run:
cd C:/Users/ryo-n/Codex_dev/memx-core/memx_spec_v3/go && go run ./cmd/mem in journal --title "<auto-generated title>" --body "<log content>" --scope "<scope>" --sensitivity internal
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.
- 4d ago First seen · 33 lines · 0 tokens per session scan A 227f98f19d7e
journal is a command published in the GitHub repository RNA4219/memx-core (23 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 198 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
projects
View your Claude Code projects tracked by EverMem.
ask
Ask a question about past work. Searches memories and combines with current context to answer.
debug
View EverMem debug logs to troubleshoot memory saving and retrieval issues.
help
Get help with EverMem plugin setup and available commands.
hub
Open the EverMem Memory Hub to view statistics, search memories, and explore timeline.
search
Search EverMem for relevant memories from past sessions.