find-related-work

find-related-work is a skill for Claude Code from chrismbryant/claude-journal-mcp. It costs 23 tokens per session (1,344 once invoked), scanned A, original, MIT.

A search tool for the project journal, where notes about earlier work, decisions, solutions, and problems are stored. It finds entries related to the task you are working on.

In plain words
What is it for?
Use it when a task resembles previous work, when choosing an architecture or library, when troubleshooting a familiar problem, or when the user asks what was done before.
Why use it?
It reduces repeated investigation and helps keep new technical choices and fixes consistent with earlier work.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

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

Good fit Use it when a task resembles previous work, when choosing an architecture or library, when troubleshooting a familiar problem, or when the user asks what was done before.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrismbryant/claude-journal-mcp/find-related-work
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.

Any agent
npx skills add chrismbryant/claude-journal-mcp --skill find-related-work
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 find-related-work

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrismbryant/claude-journal-mcp/find-related-work"><img src="https://agentmods.dev/badge/skills/chrismbryant/claude-journal-mcp/find-related-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,344 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.00023 $0.01344
Opus 5 $0.00012 $0.00672
Sonnet 5 $0.00005 $0.00269
Haiku 4.5 $0.00002 $0.00134

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

Security

Grade A, and why

find-related-work 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.

skills/find-related-work/SKILL.md · 213 lines

How it starts

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

You have the ability to search the journal for past work related to the current task.

When to Use This Skill

Use this skill proactively when:

  1. Facing similar problems

    • Current task resembles past work
    • User asks to implement something you may have done before
    • Pattern recognition suggests related history
  2. Making technical decisions

    • Architecture choices similar to past decisions
    • Technology selection (libraries, frameworks)
    • Design patterns or approaches
  3. Troubleshooting issues

    • Bug seems familiar
    • Similar error messages or symptoms
    • Related to previously fixed issues
  4. Building on past work

    • Extending existing features
    • Integrating with previous implementations
    • Following established patterns
  5. User explicitly asks

    • "Have we done something like this before?"
    • "When did we implement X?"
    • "How did we solve Y last time?"
    • "Find anything about Z"

Method 1: Keyword search

journal_search(
  query="authentication",  # Technology, concept, or feature
  limit=10
)

Method 2: Time-based search

journal_time_query(
  time_expression="last month",
  query="caching"  # Optional: narrow down results
)

Method 3: Project-specific search

journal_search(
  query="database migration",
  project="my-api"  # Focus on specific project
)

Method 4: Project history

journal_list_recent(
  project="mobile-app",
  limit=20  # Get comprehensive project context
)

Search Strategies

Broad to narrow:

  1. Start with general terms ("auth", "cache")
  2. Narrow if too many results ("OAuth2", "Redis cache")
  3. Add project filter if needed

Technology-focused:

  • Framework names: "React", "FastAPI", "PostgreSQL"
  • Library names: "JWT", "Redis", "SQLAlchemy"
  • Tool names: "Docker", "GitHub Actions", "pytest"

Concept-focused:

  • Features: "authentication", "notifications", "file upload"
  • Patterns: "caching", "rate limiting", "error handling"
  • Operations: "deployment", "migration", "refactoring"

Read the full file on GitHub · 213 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 · 213 lines · 23 tokens per session scan A a83515ef93cb

Subscribe to this mod's changes

find-related-work is a skill published in the GitHub repository chrismbryant/claude-journal-mcp (6 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 1,344 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.

Related

Other skills, from other repositories

memory-management

Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.

ThinkInAIXYZ/deepchat · 26 tokens

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.

vellum-ai/vellum-assistant · 63 tokens

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.

Dataojitori/nocturne_memory · 48 tokens

memorix-sessions

Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.

AVIDS2/memorix · 31 tokens

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…

smixs/iva-agent · 106 tokens

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…

agentfront/frontmcp · 124 tokens