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.
npx skills add chrismbryant/claude-journal-mcp --skill journal-capturegit 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/skills/chrismbryant/claude-journal-mcp/journal-capture)<a href="https://agentmods.dev/skills/chrismbryant/claude-journal-mcp/journal-capture"><img src="https://agentmods.dev/badge/skills/chrismbryant/claude-journal-mcp/journal-capture/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/skills/chrismbryant/claude-journal-mcp/journal-capture"><img src="https://agentmods.dev/badge/skills/chrismbryant/claude-journal-mcp/journal-capture.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.00015 | $0.01034 |
| Opus 5 | $0.00008 | $0.00517 |
| Sonnet 5 | $0.00003 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
journal-capture 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journal Capture Skill
You have the ability to proactively capture significant work into the user's journal.
When to Use This Skill
Use this skill automatically and proactively when you:
-
Complete a significant feature or task
- Implemented new functionality
- Fixed a complex bug
- Refactored important code
- Set up infrastructure or tooling
-
Make important technical decisions
- Chose between architectural approaches
- Selected libraries or frameworks
- Decided on implementation strategies
- Resolved design tradeoffs
-
Solve challenging problems
- Debugged difficult issues
- Overcame technical obstacles
- Found non-obvious solutions
- Learned something valuable
-
Make progress on projects
- Completed a phase of work
- Reached a milestone
- Integrated multiple components
- Finished testing or deployment
How to Capture
Use the journal_auto_capture MCP tool:
journal_auto_capture(
title="Brief title of what was accomplished",
description="The goal (what we were trying to do) and what was done"
)
The tool automatically:
- Determines the project (if in a git repo)
- Adds the "auto-capture" tag
- Generates relevant tags based on content
- Creates a structured journal entry
Examples
Example 1: Feature implementation
User: "Add authentication to the API"
[You implement OAuth2 with JWT tokens]
→ journal_auto_capture(
title="Implemented OAuth2 authentication",
description="User requested API authentication. Implemented OAuth2 flow with JWT tokens for secure user sessions."
)
Example 2: Bug fix
User: "The cache is leaking memory"
[You identify and fix the leak]
→ journal_auto_capture(
title="Fixed cache memory leak",
description="User reported memory leak in cache. Identified and fixed by implementing automatic clearing of stale entries."
)
Example 3: Technical decision
User: "Should we use Redis or PostgreSQL for caching?"
[Discussion leads to Redis choice]
→ journal_auto_capture(
title="Chose Redis for caching",
description="Evaluated Redis vs PostgreSQL for caching needs. Selected Redis due to better performance for our use case."
)
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 · 151 lines · 15 tokens per session scan A 32dafd876a05
journal-capture is a skill published in the GitHub repository chrismbryant/claude-journal-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 1,034 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
memory-management
Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memory-processor
Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…
frontmcp-extensibility
Use when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools. Covers VectoriaDB for in-memory semantic and vector search (ML-based embeddings or TF-IDF keyword engines, with persistence) and the tamper-evident, hash-chained skill…