What is ctx-agent-history-search?

A local search tool for finding relevant information in earlier coding-agent sessions, such as decisions, attempts, and transcripts.

Use it to search past sessions for commands, timelines, user intent, failures, and source references. It can also research a historical topic across those sessions.

It helps recover useful context before starting work, so you do not repeat failed approaches or miss earlier decisions.

How takuyaw-w/a5sql-mcp configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to takuyaw-w/a5sql-mcp. 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/takuyaw-w/a5sql-mcp/main/.agents/skills/ctx-agent-history-search/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/takuyaw-w/a5sql-mcp

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/takuyaw-w/a5sql-mcp/ctx-agent-history-search/github.svg)](https://agentmods.dev/skills/takuyaw-w/a5sql-mcp/ctx-agent-history-search)

Your own site

<a href="https://agentmods.dev/skills/takuyaw-w/a5sql-mcp/ctx-agent-history-search"><img src="https://agentmods.dev/badge/skills/takuyaw-w/a5sql-mcp/ctx-agent-history-search/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/takuyaw-w/a5sql-mcp/ctx-agent-history-search"><img src="https://agentmods.dev/badge/skills/takuyaw-w/a5sql-mcp/ctx-agent-history-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,751 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.01751
Opus 5.5	$0.00014	$0.00700
Sonnet 5.5	$0.00007	$0.00350
Haiku 4.5	$0.00003	$0.00175

Measured 2mo ago against content hash b374433f7b64, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

ctx-agent-history-search scanned grade C with 2 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 2mo 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -fsSL https://ctx.rs/install | sh

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://ctx.rs/install | sh

.agents/skills/ctx-agent-history-search/SKILL.md · 206 lines

How it starts

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

ctx Agent History Search

Use ctx whenever you need to reference previous coding-agent sessions. Those transcripts can contain user intent, decisions, previous work timelines, past attempts, and what worked or failed.

Use this skill in two modes:

retrieval before work, when prior sessions may contain decisions, commands, failures, or source citations that affect the current task;
history research reports, when the user asks an agent or read-only subagent to research a historical topic across prior local agent sessions.

Prerequisites

Require the ctx CLI to be installed and set up. If it is missing and installing tools is appropriate for the task, install it with:
```
curl -fsSL https://ctx.rs/install | sh
```
First setup can take time while ctx indexes past sessions. If needed, keep it running in the background or in tmux, or wait for it to finish.
If ctx remains unavailable, say local history search is unavailable and do not invent results.

Workflow

Confirm ctx is ready when starting from a cold context:
```
ctx status
ctx sources
```
Use ctx status --json or ctx sources --json only when a script needs exact fields.
Search with normal language first. Add terms or filters when useful:
```
ctx search "<query>"
ctx search "<query>" --refresh off
ctx search "<query>" --provider codex
ctx search "<query>" --workspace <workspace>
ctx search "<query>" --file <path>
ctx search "<query>" --since 30d
ctx search "<query>" --term "<related term>" --term "<error text>"
ctx search "<query>" --session <ctx-session-id>
ctx search "<query>" --verbose
```
Use default text output for agent reading. Do not add --json for search, show, or locate unless you are piping it into jq or a script, or you need exact machine-readable fields. JSON output is much larger and can quickly consume the context window.

When the prompt asks for a topic history or report across multiple sessions, run several ctx search queries with different wording and filters to find promising sessions. Use scoped ctx search "<query>" --session <ctx-session-id> when a session looks relevant and you need dense event-level matches from that session.

Read the full file on GitHub · 206 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.

2mo ago First seen · 206 lines · 34 tokens per session scan C b374433f7b64

Subscribe to this mod's changes

ctx-agent-history-search is a skill published in the GitHub repository takuyaw-w/a5sql-mcp (1 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,751 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Memory and context

ctx-agent-history-search next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ctx-agent-history-searchtakuyaw-w/a5sql-mcp	Skill	1	3mo ago	MIT	C	34	Claude Code, Codex
knowledge-ingestopenclaw/openclaw	Skill	394k	yesterday	MIT	A	80	Claude Code, Codex
mem0-oss-to-platformmem0ai/mem0	Skill	68k	2d ago	Apache-2.0	A	217	Claude Code, Codex
forgetasgeirtj/system_prompts_leaks	Skill	71k	2d ago	CC0-1.0	A	74	Claude Code, Codex
Cortexdanielmiessler/LifeOS	Skill	20k	yesterday	MIT	A	184	Claude Code
memoryopensquilla/opensquilla	Skill	7.1k	6d ago	Apache-2.0	A	44	Claude Code, Codex
ha-data-storesshiwenwen/hope-agent	Skill	1.9k	yesterday	MIT	A	115	Claude Code, Codex

a5sql-mcp: Skill for Claude Code