transcript-grep
Search a Claude Code session transcript for a string or regex pattern and show every matching message with surrounding context. Reads /api/sessions/:id/transcript and resolves sessions via /api/sessions?limit= from the Agent Monitor dashboard. Use when hunting for a specific message, prompt, tool call, or error inside a session's conversation.
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill transcript-grep --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Transcript Grep Find where a pattern appears in a session transcript and show the matches in context. ## Input The user provides: **$ARGUMENTS** Interpreted as a session reference plus a search pattern, e.g. `<session-id> "rate limit"` or `latest TypeError`. Parsing rules: - The session reference is the first token if it looks like an id, or the words `latest`/`last` (most recently updated session). - The remainder is the search pattern (string or regex, quoted if it contains spaces). - If no session is given, default to the most recent session. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/sessions?limit=N` | session list to resolve `latest`/`last` and to confirm the id exists | | `GET /api/sessions/:id/transcript` | the ordered transcript messages (role, content, tool calls/results, timestamps) for the session | ## Report Sections ### 1. Resolve the session If `latest`/`last` (or no id), call `GET /api/sessions?limit=1`. Otherwise verify the id with `GET /api/sessions?limit=1000` (or `GET /api/sessions/:id`). Report the resolved id, status, and model before searching. ### 2. Fetch and search Call `GET /api/sessions/:id/transcript`. Walk the messages
- Input
- Data Sources
- Report Sections
- 1. Resolve the session
- 2. Fetch and search
- 3. Matches with context
- 4. Summary
- Output
What does the transcript-grep skill do?
Search a Claude Code session transcript for a string or regex pattern and show every matching message with surrounding context. Reads /api/sessions/:id/transcript and resolves sessions via /api/sessions?limit= from the Agent Monitor dashboard. Use when hunting for a specific message, prompt, tool call, or error inside a session's conversation.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill transcript-grep --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.