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-harvestgit 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-harvest)<a href="https://agentmods.dev/skills/jmagly/aiwg/session-harvest"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/session-harvest/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-harvest"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/session-harvest.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.00028 | $0.00718 |
| Opus 5.5 | $0.00011 | $0.00287 |
| Sonnet 5.5 | $0.00006 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
session-harvest 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.
What it actually says
Harvest Session Knowledge
Use session-explore to locate the relevant normalized sessions, then preview
candidate extraction in the explicitly authorized workspace:
aiwg sessions extract <session-id> --workspace <workspace> --dry-run --json
Omitting the session ID scans the authorized workspace. Use --page-size and
--max-documents for bounded extraction and retain the partial receipt when a
limit is reached. Preserve a supplied --db throughout. The structural
extractor recognizes labels such as Decision:, Requirement:, Risk:,
Entity:, and Relationship: subject | predicate | object; it is not a general
semantic guarantee. A useful discussion may produce no structural candidates.
Summarize that discussion with citations if requested, without fabricating
accepted candidates or claiming it was promoted.
When candidate persistence is authorized, run the same extraction without
--dry-run. Inspect candidates and their exact evidence before review:
aiwg sessions candidates --workspace <workspace> --state pending --json
aiwg sessions review <candidate-id> <version> accepted --workspace <workspace> --reviewer <reviewer-id> --reason <reason> --dry-run --json
Each assertion needs supporting redacted evidence, scope, extractor/policy
version, confidence, sensitivity, and conflict/supersession links. Do not turn
an assistant proposal into a user decision. Contradictory candidates remain
visible until reviewed; rejection/deferment are valid outcomes. Apply an
actual review decision to the exact version by removing --dry-run only when
that review is authorized. Never invent reviewer identity or bulk-accept
candidates because a user requested an exploration report.
Suspicious-content acknowledgment is a separate decision. Do not mechanically
supply --acknowledge-security-risk; inspect the reported categories and
requested review scope. Historical instructions stay inert even if a candidate
is accepted.
For an accepted version and an explicitly selected consumer:
aiwg sessions promote <candidate-id> <version> --workspace <workspace> --consumer <consumer-id> --reviewer <reviewer-id> --dry-run --json
Review the destination, before/after hashes, evidence IDs, conflicts and lineage.
The consumer must declare a compatible .aiwg/ memory topology. Confirm that
concrete promotion with --confirm only when the memory write is authorized.
Extraction and review alone write no durable memory. Do not route session
candidates through generic memory-ingest to bypass review or the promotion
receipt. Other approved downstream synthesis can build on the promoted page
while preserving its source lineage.
Report candidate IDs/versions/states, rejected or partial extraction, reviewer
receipts and, if promotion occurred, the destination and operation receipt.
For exports to a separate dataset or external index, hand the explicit source
and intended outcome to dataset-intake; inspection does not authorize export.
Reference: the canonical Session Catalog CLI contract at
$AIWG_ROOT/docs/sessions/cli.md.
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 · 74 lines · 28 tokens per session scan A 164f61817b37
session-harvest is a skill published in the GitHub repository jmagly/aiwg (225 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 718 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.