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/chrismbryant/claude-journal-mcpWrote 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/chrismbryant/claude-journal-mcp/journal-recent)<a href="https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-recent"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-recent/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/chrismbryant/claude-journal-mcp/journal-recent"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-recent.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.00441 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
journal-recent 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 12d 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
Show Recent Journal Entries
You are helping the user view their recent journal entries.
This command is especially useful after /clear to restore context about recent work.
Process
-
Determine scope:
- Ask how many recent entries to show (default: 10)
- Ask if they want to filter by project
-
Use the MCP tool: Call
journal_list_recent:journal_list_recent( limit=10 (or user's preference), project="project-name" (optional) ) -
Present results:
- Show entries chronologically (newest first)
- Highlight key information:
- Date/time
- Project name
- Title
- Brief description
- Include entry IDs for reference
- Summarize what they were working on
Use Cases
After /clear:
User: "What was I working on?"
→ journal_list_recent(limit=10)
→ Summarize: "You were recently working on X, Y, and Z"
Start of day:
User: "What did I do yesterday?"
→ journal_list_recent(limit=20)
→ Filter to yesterday's entries and summarize
Project context:
User: "Show recent work on my-api"
→ journal_list_recent(project="my-api", limit=15)
Presentation Format
Present entries like:
**Recent Journal Entries** (10 shown)
[42] Implemented OAuth login (2024-01-15 14:30)
📁 my-app | 🏷️ auth, oauth
Built OAuth2 flow with JWT tokens for user authentication
[41] Fixed cache memory leak (2024-01-15 10:15)
🏷️ bugfix, performance
Cache wasn't clearing old entries, causing gradual memory growth
...
Context Recovery Tips
After showing entries, help user:
- "You were focusing on authentication in my-app"
- "Last thing was fixing a performance issue"
- "Ready to continue where you left off?"
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.
- 12d ago First seen · 77 lines · 0 tokens per session scan A 268a5175d3fd
journal-recent is a command published in the GitHub repository chrismbryant/claude-journal-mcp (6 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 441 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-31.
Other commands, from other repositories
suggest-automation
A command that reviews recent Git commits and project instructions to find work patterns that happen repeatedly.
instinct-export
Export instincts for sharing with teammates or other projects.
adhoc-flow
Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
implement
Multi-agent advisory squad workflow for implementing code changes: classify → score risk → select agents → planner → Gate 1 (plan approval) → advisory squad → Gate 2 (Blocker halt) → implementer → consolidator → verdict. Auto-detects depth (quick/normal/deep) from risk + file count; pass --quick or --deep to override.…
vouch
Show RunVouch status of all scheduled agents and open alerts.