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 skills add jmagly/aiwg --skill session-exploregit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/skills/jmagly/aiwg/session-explore)<a href="https://agentmods.dev/skills/jmagly/aiwg/session-explore"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/session-explore/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.
<a href="https://agentmods.dev/skills/jmagly/aiwg/session-explore"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/session-explore.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.01180 |
| Opus 5.5 | $0.00010 | $0.00472 |
| Sonnet 5.5 | $0.00005 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
session-explore 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore Session History
Answer the user's question from the normalized aiwg sessions catalog. Start
from their topic, time window, provider, workspace, or known session; they do
not need to know catalog terminology. This is historical inspection, not the
singular aiwg session launcher or permission to replay recorded commands.
Scope and first reads
Use the current project when unambiguous. Preserve a supplied --db on every
call. Ask only when workspace identity, intended data scope, or a necessary
source is missing. Inspect aiwg sessions sources --json and
aiwg sessions doctor --json, then list the authorized workspace:
aiwg sessions list --workspace <workspace> --limit 50 --json
Check data.coverage before interpreting an empty result. Missing, stale,
export-required, rejected, or pending histories are gaps, not proof that no
activity occurred. Follow a concrete availability diagnostic; do not install
a runtime, scan shared provider roots, import histories, or broaden the
workspace merely to make a query succeed. If acquisition is requested, use the
acquisition recipe.
Choose the smallest useful query
Read the relevant recipes for exact supported filters:
| User need | Route |
|---|---|
| Find a discussion, decision, file reference, error, person, or topic | Lexical search, then show the cited sessions |
| Reconstruct when work happened or resume context | Cross-provider timeline, cited search, and bounded summary |
| Compare providers, models, roles, periods, or sessions | Matched search/analytics filters with explicit denominators |
| Diagnose retries, failed tools, escalations, or human intervention | analytics summary, tool-calls, escalations, hitl |
| Investigate instruction/control traffic or incident evidence | Control-event filters; forensic views only with explicit authorization |
| Find reusable requirements, decisions, risks, entities, relationships | session-harvest preview and candidate review |
| Explain imports, mutations, tombstones, or missing history | Coverage, doctor, and content-free audit; lifecycle recipe |
| Find expensive work | Correlate catalog evidence with cost-history; tool counts are not spend |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 106 lines · 25 tokens per session scan A 31b3b51f29eb
session-explore is a skill published in the GitHub repository jmagly/aiwg (225 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,180 once invoked, about $0.0001 per session on Opus 5.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-09-08.
Other skills, from other repositories
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
lore
Curating cross-agent knowledge and institutional memory: extracts patterns from agent journals into METAPATTERNS.md, detects knowledge decay, propagates best practices. Use for memory curation.
multi-platform-messenger-bridge
Unify WhatsApp, Telegram, and future channels with shared conversation context and message-quality assessment. Use for: bridge messengers, unified chat memory, cross-platform reply, WhatsApp responder.
mega-context-manager
Manages large context windows via chunking, summarization, and retrieval. Use for: manage context, too much context, chunk document, context budget.
memory-sanitizer
Scores and filters retrieved memory against trust and poisoning risk. Use for: sanitize memory, trust score retrieval, clean knowledge graph, semantic-memory-manager.
persistent-memory-bridge
Bridges session memory to persistent storage across conversations. Use for: remember this, persistent memory, save to memory, recall later.