journal-time

journal-time is a command for Claude Code from chrismbryant/claude-journal-mcp. It costs 0 tokens per session (612 once invoked), scanned A, original, MIT.

A journal search command for finding entries by dates or time periods, such as yesterday, last week, January, or a specific date.

In plain words
What is it for?
Use it to review recent work, find when a feature was implemented, or search a project journal within a chosen period.
Why use it?
It avoids manually scanning journal entries to remember what you worked on or when something happened.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-journal plugin — 3 skills, 6 commands, 1 hook shipped together

Good fit Use it to review recent work, find when a feature was implemented, or search a project journal within a chosen period.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/chrismbryant/claude-journal-mcp/journal-time
Install

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.

Clone the repo
git clone --depth 1 https://github.com/chrismbryant/claude-journal-mcp

Made for: Claude Code.

Or install claude-journal, the plugin that ships this one along with the rest of its 3 skills, 6 commands, 1 hook.

Wrote 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.

agentmods badge for journal-time

README.md
[![agentmods](https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-time/github.svg)](https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-time)
Your own site
<a href="https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-time"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-time/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.

agentmods 80×15 button for journal-time

Your own site · 80×15
<a href="https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-time"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-time.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00612
Opus 5 $0.00000 $0.00306
Sonnet 5 $0.00000 $0.00122
Haiku 4.5 $0.00000 $0.00061

Measured 12d ago against content hash cb1dbe54c8d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

journal-time 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.

commands/journal-time.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Time-Based Journal Query

You are helping the user query journal entries by time period.

This command uses natural language time expressions to find entries.

Process

  1. Understand the time query: User might ask in various ways:

    • "What did I work on last week?"
    • "Show me entries from January"
    • "When did I implement feature X?"
    • "What happened yesterday?"
  2. Extract time expression: Supported formats:

    • Relative: "yesterday", "today", "last week", "last month", "last year"
    • Recent periods: "last 3 days", "last 2 weeks"
    • Current periods: "this week", "this month", "this year"
    • Month names: "january", "january 2024"
    • ISO dates: "2024-01-15"
  3. Use the MCP tool: Call journal_time_query:

    journal_time_query(
      time_expression="last week",
      query="optional search terms" (if looking for something specific),
      project="project-name" (optional)
    )
    
  4. Present results:

    • Show entries within the time range
    • Highlight what they accomplished
    • Group by day or week if many results
    • Summarize patterns or themes

Examples

Example 1: Recent past

User: "What did I do last week?"
→ journal_time_query(time_expression="last week")
→ Present all entries from last week

Example 2: Specific search in time range

User: "When did I work on authentication?"
→ journal_time_query(time_expression="last month", query="authentication")
→ Find auth-related entries from last month

Example 3: Historical lookup

User: "Show me what I did in January"
→ journal_time_query(time_expression="january")
→ All January entries

Example 4: Project timeline

User: "What have I done on my-api this year?"
→ journal_time_query(time_expression="this year", project="my-api")

Presentation Format

Present with time context:

**Journal Entries: Last Week** (15 found)

Week of Jan 8-14, 2024

Monday, Jan 8:
- [45] Implemented OAuth login (my-app)
- [44] Set up testing framework

Tuesday, Jan 9:
- [43] Fixed cache memory leak
...

Read the full file on GitHub · 94 lines

Changes

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.

  1. 12d ago First seen · 94 lines · 0 tokens per session scan A cb1dbe54c8d3

Subscribe to this mod's changes

journal-time 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 612 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.