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.
npx agentmods add commands/vaibhavaher100/wrap-session/wrap-listgit clone --depth 1 https://github.com/VaibhavAher100/wrap-sessionWrote 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.
[](https://agentmods.dev/commands/vaibhavaher100/wrap-session/wrap-list)<a href="https://agentmods.dev/commands/vaibhavaher100/wrap-session/wrap-list"><img src="https://agentmods.dev/badge/commands/vaibhavaher100/wrap-session/wrap-list.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00402 |
| Opus 5 | $0.00000 | $0.00201 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
wrap-list 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.
What it actually says
List all recorded sessions as a summary table. Execute immediately, no confirmation needed.
Step 1 — Check for index file
Use the Bash tool:
wc -l logs/sessions/_index.jsonl 2>/dev/null || echo "no-index"
Step 2 — Build the table
If logs/sessions/_index.jsonl exists (fast path):
Read logs/sessions/_index.jsonl. Each line is a JSON object with fields: session_id, date, summary, confidence, tags, files_changed, open_items. Build the table directly from these fields — no file scanning needed.
If logs/sessions/_index.jsonl is missing (fallback — scan frontmatter):
Use the Bash tool:
ls logs/sessions/*.md 2>/dev/null | grep -v "_index" | sort
For each file, read only the frontmatter (lines between the --- delimiters). Extract: session_id, session_date, summary, confidence, files_changed, open_items.
Step 3 — Output
Output a markdown table:
| Session | Date | Summary | Confidence | Files | Open |
|---|---|---|---|---|---|
<id> |
YYYY-MM-DD | high/med/low/— | N | N |
Rules:
- Truncate summary to 80 chars if longer
- If
confidencefield is absent (pre-schema sessions), show— - Sort rows by session ID ascending (oldest first)
- After the table, print one line:
Total: N sessions across D distinct dates - If index was used: append
(source: logs/sessions/_index.jsonl)— if frontmatter scan was used: append(source: frontmatter scan — run /wrap to build index)
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.
- 4d ago First seen · 45 lines · 0 tokens per session scan A cf7e52e7e32c
wrap-list 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 402 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.
Other commands, from other repositories
peers
List bridger peers — who is addressable, where, and what they're doing.
ask
Ask a peer session a question and wait for its answer.
monitor
Open the read-only web view of peers, threads and bus health.
register
Register this project directory as a named bridger peer.
send
Send a message to a peer session.
status
Show bridger identity, peers, and unread message counts.