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-export)<a href="https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-export"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-export/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-export"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-export.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.00500 |
| Opus 5 | $0.00000 | $0.00250 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
journal-export 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export Journal
You are helping the user export their journal for backup or sharing.
Process
-
Determine export path:
- Ask if they want a specific file path
- If not specified, tool auto-generates:
journal_export_YYYYMMDD_HHMMSS.db - Suggest a descriptive name if backing up:
journal_backup_2024-01-15.db
-
Use the MCP tool: Call
journal_export:journal_export( file_path="path/to/export.db" (optional) ) -
Confirm and provide instructions:
- Show where file was saved
- Explain how to import on another machine
- Mention it's a complete SQLite database
Use Cases
Backup:
User: "Backup my journal"
→ journal_export(file_path="journal_backup_2024-01-15.db")
→ "Saved to journal_backup_2024-01-15.db"
Sharing between machines:
User: "Export journal to share with my laptop"
→ journal_export()
→ "Saved to journal_export_20240115_143052.db"
→ "Transfer this file and use /journal-import on your laptop"
Archiving:
User: "Archive my journal"
→ journal_export(file_path="~/archives/journal_2024.db")
→ Confirm saved location
Post-Export Instructions
After export, tell the user:
✅ Journal exported to: [file path]
**To import on another machine:**
1. Transfer the file (USB drive, cloud storage, etc.)
2. On the other machine, run: `/journal-import path/to/file.db`
3. Entries will be merged (no duplicates)
**Backup Tips:**
- Export regularly for safety
- Store backups in multiple locations
- File is portable SQLite database
- Works across different operating systems
Format Details to Share
Explain the export format:
- Standard SQLite database
- Can open with any SQLite tool
- Contains all entries, tags, timestamps
- Schema-compatible across versions
- No proprietary formats or encryption
Safety Reminders
- Exported file contains all journal content
- Store securely (may contain sensitive work info)
- Can view/edit with SQLite browser tools if needed
- No data loss on export (original stays intact)
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.
- 10d ago First seen · 83 lines · 0 tokens per session scan A bd15c181479e
journal-export 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 500 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.
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.
analyze-email
Quick analysis of a single email. Read metadata, summarize content, and list attachments.