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-add)<a href="https://agentmods.dev/commands/chrismbryant/claude-journal-mcp/journal-add"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-add/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-add"><img src="https://agentmods.dev/badge/commands/chrismbryant/claude-journal-mcp/journal-add.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.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
journal-add 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.
What it actually says
Add Journal Entry
You are helping the user add a journal entry.
Process
-
Gather information:
- Title (required): Ask for a brief title
- Description (required): Ask for 1-2 sentence description
- Project (optional): Ask if this is related to a specific project/repo
- If user is in a git repo, suggest using the repo name
- If not specified, can be left empty
- Tags (optional): Suggest relevant tags based on the content
- Technical terms mentioned
- Type of work (feature, bugfix, refactor, etc.)
- Technologies used
-
Use the MCP tool: Call
journal_addwith the gathered information:journal_add( title="User's title", description="User's description", project="project-name" (if provided), tags=["tag1", "tag2"] (if provided) ) -
Confirm success: Tell the user their entry was saved and show the ID for reference.
Examples
Example 1: Simple entry
- Title: "Implemented OAuth login"
- Description: "Built OAuth2 flow with JWT tokens for user authentication"
- Project: "my-app"
- Tags: ["auth", "oauth", "backend"]
Example 2: Bug fix
- Title: "Fixed memory leak in cache"
- Description: "Cache wasn't clearing old entries, causing gradual memory growth"
- Tags: ["bugfix", "performance", "cache"]
Tips
- Suggest concise titles (3-7 words)
- Descriptions should be complete sentences
- Tags help with searching later
- Project name helps organize multi-repo work
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 · 51 lines · 0 tokens per session scan A d3c53b786432
journal-add 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 374 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.