jules: Skill for Claude Code

.claude/skills/search-history/SKILL.md

search-history is a skill for Claude Code from jonathanmalkin/jules. It costs 114 tokens per session (1,248 once invoked), scanned A, original, MIT.

A search tool for structured records of past coding sessions, such as reports, issues, retrospectives, plans, research notes, and decision logs.

In plain words
What is it for?
Searching session history by keywords, document type, and date, including questions about when a decision or plan was made.
Why use it?
It helps you find earlier project context without manually opening every session document.

Skill for Claude Code

Written for Claude Code: effort in frontmatter.

This is jonathanmalkin/jules's own configuration. It tells Claude Code how to work on jules itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jules configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jonathanmalkin/jules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jonathanmalkin/jules/main/.claude/skills/search-history/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jonathanmalkin/jules

Made for: Claude Code.

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 search-history

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathanmalkin/jules/search-history/github.svg)](https://agentmods.dev/skills/jonathanmalkin/jules/search-history)
Your own site
<a href="https://agentmods.dev/skills/jonathanmalkin/jules/search-history"><img src="https://agentmods.dev/badge/skills/jonathanmalkin/jules/search-history/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 search-history

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonathanmalkin/jules/search-history"><img src="https://agentmods.dev/badge/skills/jonathanmalkin/jules/search-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,248 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.00114 $0.01248
Opus 5 $0.00057 $0.00624
Sonnet 5 $0.00023 $0.00250
Haiku 4.5 $0.00011 $0.00125

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

Security

Grade A, and why

search-history 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/test-search-history.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/search-history/SKILL.md · 106 lines

How it starts

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

Search structured wrap-up output and field notes across eight document types. Complementary to claude-history (which searches raw conversation JSONL).

Step 1: Parse Query

Extract from the user's input:

  • Keywords: the search terms (everything that isn't a flag)
  • --type filter (optional): one of reports, issues, retros, memory, plans, research, decisions, evolution, or all. Default: all.
  • --since YYYY-MM-DD (optional): only include files dated on or after this date. Applies to all dated file types (reports, issues, retros, memory, plans, research). Does not apply to Decision Log or System Evolution (single files, always searched in full). Default: no date filter.

If the input is just /search-history with no keywords, ask what to search for.

Step 2: Search Targets

Eight document types with their glob patterns:

Type Key Label Glob Pattern Dated?
reports Session Reports Documents/Field-Notes/Logs/*-Session-Report*.md Yes
issues Session Issues Documents/Field-Notes/Logs/*-Session-Issues*.md Yes
retros Session Retros Documents/Field-Notes/Logs/*-Session-Retro*.md Yes
memory Memory Syntheses Documents/Field-Notes/Logs/*-Memory-Synthesis*.md Yes
plans Plans Documents/Field-Notes/Plans/*.md Yes
research Research Docs Documents/Field-Notes/Research/*.md Yes
decisions Decision Log Documents/Field-Notes/Decision-Log.md No
evolution System Evolution Documents/System/System-Evolution.md No

When --type is specified, search only that type. Otherwise search all eight.

For each active document type:

  1. Glob to find matching files.
  2. For dated types (reports, issues, retros, memory, plans, research): if --since is set, filter filenames by date prefix (YYYY-MM-DD >= since date). Files without a parseable date prefix are included.
  3. Grep for keywords across the matched files. Use case-insensitive search. Request content output mode with 2 lines of context (-C 2).
  4. For Decision Log and System Evolution (single files): --since is NOT applied — always search the full file.

Read the full file on GitHub · 106 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 106 lines · 114 tokens per session scan A 6df874bc1428

Subscribe to this mod's changes

search-history is a skill published in the GitHub repository jonathanmalkin/jules (65 stars, last pushed 3mo ago), licensed MIT. It adds 114 tokens to every session and 1,248 once invoked, about $0.0006 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-30.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

shellm

Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.

laude-institute/headlong · 49 tokens