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-stats)<a href="https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-stats"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-stats/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-stats"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-stats.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.00515 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
journal-stats 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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Statistics
You are helping the user view statistics about their journal.
Process
-
Use the MCP tool: Call
journal_stats(no parameters needed):journal_stats() -
Present insights: The tool returns:
- Total number of entries
- Date range (first to last entry)
- Number of projects tracked
- Entries per project breakdown
-
Add interpretation:
- Highlight most active projects
- Show how long they've been journaling
- Suggest actions based on stats
Presentation Format
**📊 Journal Statistics**
**Overview:**
- **Total Entries:** 247 entries
- **Journaling Since:** January 15, 2024 (6 months)
- **Last Entry:** July 20, 2024
- **Projects Tracked:** 5 projects
**Entries by Project:**
1. my-app: 89 entries (36%)
2. api-service: 62 entries (25%)
3. website: 51 entries (21%)
4. mobile-app: 31 entries (13%)
5. internal-tools: 14 entries (6%)
**Insights:**
- Most active on my-app - main focus recently
- Consistent journaling over 6 months
- Good project organization across 5 repos
Additional Actions to Suggest
Based on stats, suggest:
If many entries:
- "Want to search for something specific? Try
/journal-search" - "Interested in recent work? Try
/journal-recent"
If few entries:
- "Keep journaling! It gets more valuable over time"
- "Consider using auto-capture to save more context"
If uneven distribution:
- "my-app has lots of entries - want to see them?
/journal-search project:my-app"
If stale (last entry old):
- "Haven't journaled recently - anything to capture?
/journal-add"
Use Cases
Project planning:
User: "How much have I worked on each project?"
→ journal_stats()
→ Show breakdown by project
Progress tracking:
User: "How long have I been using the journal?"
→ journal_stats()
→ Highlight date range and growth
General overview:
User: "Give me an overview of my journal"
→ journal_stats()
→ Full statistics with insights
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.
- 11d ago First seen · 89 lines · 0 tokens per session scan A c26a7e734fb7
journal-stats 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 515 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
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
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.
infinite
INFINITE AGENTIC LOOP COMMAND.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
checklist
Generate a custom checklist for the current feature based on user requirements.