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 skills/ai-ecoverse/slicc/transcript-exportnpx skills add ai-ecoverse/slicc --skill transcript-exportgit clone --depth 1 https://github.com/ai-ecoverse/sliccWrote 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/ai-ecoverse/slicc/transcript-export)<a href="https://agentmods.dev/skills/ai-ecoverse/slicc/transcript-export"><img src="https://agentmods.dev/badge/skills/ai-ecoverse/slicc/transcript-export.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.1 | $0.00069 | $0.01185 |
| Opus 5 | $0.00034 | $0.00593 |
| Sonnet 5 | $0.00014 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
transcript-export 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 yesterday.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transcript Export
The session export command packages the current (or a named archived)
session into a signed, redacted ZIP bundle and writes it to the VFS.
Syntax
# Export the active session (default output path):
session export
# Export to a specific VFS path:
session export --output /workspace/my-session.zip
# Export a frozen (archived) session by its ID:
session export --id <frozen-session-id>
# Export a frozen session to a custom path:
session export --id <session-id> --output /workspace/archive.zip
The default output path is /workspace/slicc-transcript-<session-id>.zip.
What the bundle contains
The ZIP always contains exactly one file: transcript.json. Its top-level
structure follows TranscriptDocumentV1 (schema version 1):
slicc-transcript-<id>.zip
└── transcript.json # full schema-validated v1 document
└── attachments/ # only if the session has binary attachments
└── <sha256>.<ext> # original bytes, unchanged
Cone and scoop conversations
transcript.json contains every conversation in the session:
conversations[].kind == "cone"— the main agent thread.conversations[].kind == "scoop"— parallel sub-agent threads.
Each conversation contains all messages in sequence order.
Redaction guarantees
The export is always redacted before the ZIP is written. Two detectors run:
| Detector | What it catches | Output in transcript.json |
|---|---|---|
known-secret |
Secrets from the session secret store | ⟦REDACTED:known-secret:<id>⟧ |
credential-pattern |
Bare API keys, bearer tokens, PEM private keys | ⟦REDACTED:credential-pattern:<id>⟧ |
Redacted values are listed in privacy.redactions[]. privacy.redactionCounts
gives per-category counts. A privacy.reasoningExcluded: true field confirms
that no reasoning/thinking content was included.
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.
- yesterday First seen · 132 lines · 69 tokens per session scan A 3e9add2cb9b8
transcript-export is a skill published in the GitHub repository ai-ecoverse/slicc (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 1,185 once invoked, about $0.0003 per session on Opus 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-05.
Other skills, from other repositories
gog-workspace
Use the gog CLI for Google Workspace tasks across Gmail, Calendar, Drive, Docs, Sheets, Contacts, and related services. Use when the user asks to check email, search Gmail, inspect calendar events, find Drive files, read Docs or Sheets, or manage Google Workspace data through gog.
pandoc
Convert documents between formats (Markdown, DOCX, HTML, PDF, RST, EPUB, LaTeX) via the pandoc CLI. Use to transform a document from one format to another.
Manipulate PDF files — merge, split, extract pages/text, PDF↔images, OCR, info — via the qpdf / poppler / ocrmypdf CLIs. Use to combine, slice, convert, or OCR PDFs.
xlsx
Create and edit Excel .xlsx workbooks (sheets, cells, formulas, formatting) via Python openpyxl. Use to generate spreadsheets or write/update cells. Reading is via os.fs.readdocument.
article-exporter
Export any web article to a local Obsidian-ready Markdown directory. Fetches page content via actionbook CLI, downloads images locally, rewrites image references to relative paths, and optionally translates the article using AI. Produces a self-contained folder with README.md, images/, and an index.md navigation file.
excel-spreadsheets
Create, modify, and manage Excel spreadsheets.