wrap-find

wrap-find is a command for coding agents from VaibhavAher100/wrap-session. It costs 0 tokens per session (371 once invoked), scanned A, original, MIT.

A command that searches saved agent session logs for an exact word or phrase and shows the matching sessions with surrounding details.

In plain words
What is it for?
Use it to locate sessions containing a specific term, then review each match’s session ID, date, summary, and matching lines.
Why use it?
It makes it easier to find past discussions or decisions without manually opening every session log.

Command

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 commands/vaibhavaher100/wrap-session/wrap-find
Clone the repo
git clone --depth 1 https://github.com/VaibhavAher100/wrap-session

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 wrap-find

README.md
[![agentmods](https://agentmods.dev/badge/commands/vaibhavaher100/wrap-session/wrap-find.svg)](https://agentmods.dev/commands/vaibhavaher100/wrap-session/wrap-find)
Your own site
<a href="https://agentmods.dev/commands/vaibhavaher100/wrap-session/wrap-find"><img src="https://agentmods.dev/badge/commands/vaibhavaher100/wrap-session/wrap-find.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 371 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00371
Opus 5 $0.00000 $0.00186
Sonnet 5 $0.00000 $0.00074
Haiku 4.5 $0.00000 $0.00037

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

Security

Grade A, and why

wrap-find 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 4d 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.

commands/wrap-find.md · 52 lines

What it actually says

Search session logs for a keyword or phrase. The search term is everything after /wrap-find in the user's message.

Execute immediately, no confirmation needed.


Assign the user's search term to a shell variable and pass it as data — do not interpolate it directly into the grep pattern string. Use -F (fixed strings) to prevent regex interpretation of the term.

Use the Bash tool:

SEARCH_TERM='<SEARCH_TERM>'
grep -riFl -- "$SEARCH_TERM" logs/sessions/ 2>/dev/null | sort

Replace <SEARCH_TERM> with the user's argument when setting the variable. If the term contains single quotes, use double quotes around the assignment instead.

Step 2 — For each matching file

Read only the frontmatter of each matching file to get session_id, session_date, and summary.

Then run a second grep to extract the matching lines with context:

SEARCH_TERM='<SEARCH_TERM>'
grep -inF -- "$SEARCH_TERM" <FILE> 2>/dev/null

Step 3 — Output results

For each matching session, output:

### <session-id> (<session-date>)
<summary>

Matches:
- Line N: <matching line>
- Line N: <matching line>

Separate each session result with a horizontal rule.

If no matches found, output: No sessions found matching "<SEARCH_TERM>".

After all results, print: Found in N of M sessions.

Notes

  • Search is case-insensitive, fixed-string (no regex)
  • Searches full file content — frontmatter, actions table, reasoning, open items
  • For tag search, user can pass e.g. career or embedded to match topic tags
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. 4d ago First seen · 52 lines · 0 tokens per session scan A ef5e94e066a1

Subscribe to this mod's changes

wrap-find is a command published in the GitHub repository VaibhavAher100/wrap-session (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 371 tokens. 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.