claude-code-search AGENTS.md

Project instructions for claude-code-search, a terminal application that searches coding-agent prompts from past Claude Code, Codex CLI, and Cursor sessions.

In plain words
What is it for?
Use them when developing, testing, formatting, or building this React-and-Ink terminal application.
Why use it?
They explain the app's build commands and terminal interface rules, including how to avoid corrupting its text-based display.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/mblode/claude-code-search/agents-md
Clone the repo
git clone --depth 1 https://github.com/mblode/claude-code-search

Made for: Codex, OpenCode.

Per session 658 This file is loaded in full into every session.
When invoked 658 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00658 $0.00658
Opus 5 $0.00329 $0.00329
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

Measured 2d ago against content hash f7922b81ae9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-code-search AGENTS.md 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 2d 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.

AGENTS.md · 56 lines

How it starts

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

ccs, a terminal UI for searching your own coding-agent prompts across past sessions — fzf or atuin, but for prompt history. Sources: Claude Code, Codex CLI, Cursor. Published to npm as claude-code-search.

Commands

npm install        # setup (requires Node >= 24.11)
npm run dev        # tsdown --watch
npm run build      # tsdown (CLI + library + dts)
npm run start      # node dist/cli.js
npm run lint       # ultracite check (oxlint + oxfmt)
npm run check      # same as lint
npm run format     # ultracite fix
npm run check:types # tsc --noEmit
npm test           # vitest run --passWithNoTests

Gates: lint, check:types, test. Smoke: npm run build && npm run start against your own history.

This is a React app that renders to a terminal

The UI is Ink, so src/app.tsx and src/components/*.tsx are React components whose output is text.

  • There is no DOM. Layout comes from Ink's <Box>; colour from src/utils/color.ts.
  • Anything written to stdout that is not Ink's render corrupts the frame. Debug to stderr or to a file. CLI data (list/search/json) is the exception: stdout is data, stderr is logs.
  • Input is ink-text-input plus raw key handling.

Build shape

tsdown.config.ts produces two entries: the binary (dist/cli.js, package.json binccs) with a shebang banner, and the library (dist/index.js + dts). Do not put a shebang in src/cli.ts.

files is dist, example.png, README, LICENSE. Check npm pack --dry-run after touching the build.

Reading session history

Never write to Claude, Codex, or Cursor history files. Parse failures are expected: skip the line, do not throw a stack at the user.

Source Layout
Claude ~/.claude/projects/<encoded-cwd>/<uuid>.jsonl (also ~/.config/claude/projects if present). Skip subagents/.
Codex ~/.codex/sessions/**/rollout-*.jsonl and archived_sessions. Skip .jsonl.zst.
Cursor Read-only state.vscdb (composerHeaders + bubbleId type 1). Cwd-scoped unless --source cursor alone.

Read the full file on GitHub · 56 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. 2d ago First seen · 56 lines · 658 tokens per session scan A f7922b81ae9a

Subscribe to this mod's changes

claude-code-search AGENTS.md is an instructions file published in the GitHub repository mblode/claude-code-search (5 stars, last pushed 12d ago), licensed MIT. It adds 658 tokens to every session, about $0.0033 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.