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 Elumenotion/GuideAnts --skill transcript-to-pdfgit clone --depth 1 https://github.com/Elumenotion/GuideAntsWrote 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/elumenotion/guideants/transcript-to-pdf)<a href="https://agentmods.dev/skills/elumenotion/guideants/transcript-to-pdf"><img src="https://agentmods.dev/badge/skills/elumenotion/guideants/transcript-to-pdf.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.01128 |
| Opus 5 | $0.00036 | $0.00564 |
| Sonnet 5 | $0.00014 | $0.00226 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
transcript-to-pdf 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
transcript-to-pdf
Paths — fixed layout, do not probe or re-derive. The sandbox CWD is the
notebook's output directory. This skill's scripts live under
Skills/transcript-to-pdf/scripts/ relative to it. Write PDF output with a
bare filename (e.g. -o report.pdf); never prefix with Output/.
Turns a markdown conversation transcript (the kind produced by saving a GuideAnts / Code-Executor session) into a well-formatted PDF.
The renderer understands the transcript system, not generic markdown: it
recognises **User** / **Assistant** / **Tool** turns, **Tool Call:**
input blocks, and tool OUTPUT JSON, and lays each out as a distinct card.
Heredoc script inputs (e.g. cat > file <<EOF) are split so the bash header
and the written-file body are highlighted with the correct language lexer.
Stdlib + weasyprint only. No network. No model download. Runs in seconds.
Dependencies
Required (already present in the sandbox image):
weasyprint # HTML -> PDF
pygments # code highlighting
pypdf # (optional) page inspection
Check with python3 -c "import weasyprint, pygments". If missing:
pip install weasyprint pygments.
What to run
Single command, one input, one output:
python3 Skills/transcript-to-pdf/scripts/md_transcript_to_pdf.py \
<transcript>.md -o <out>.pdf
- Output defaults to
<input>.pdfwhen-ois omitted. - The script prints a short report (title, turn counts, tool-call counts, fence fixes, output path) and exits 0 on success.
Useful flags
python3 .../md_transcript_to_pdf.py in.md --no-cover # drop the cover page
python3 .../md_transcript_to_pdf.py in.md --html out.html # also dump the intermediate HTML (debug)
python3 .../md_transcript_to_pdf.py in.md --quiet # suppress the report
Layout guarantees
- Cover page — title, subtitle, stat grid (messages / users / assistants /
tool calls / heredocs / source lines), metadata table, and a list of the
session's user requests. The list region is a bounded flex box
(
flex:1 1 0; min-height:0; overflow:hidden) so it cannot collide with the footer regardless of how long the session is. Snippets are capped (4 shown, "+ N more" otherwise) and shortened to ~140 chars to keep the common case clean. - Turns — every message is a role-badged card (User / Assistant / Tool).
- Tool-call inputs —
**Tool Call:**blocks are anchored to the following JSON fence; thescriptfield is unescaped and, if it is a heredoc, rendered as (bash header) + (file body in the right language) + (bash footer). - Tool outputs — the
**Tool**result JSON renders in an amber panel. - Markdown — headings, bold/italic, inline code, lists, and pipe tables.
- Truncated-fence repair — turns that end mid-code-fence get a closing fence inserted so the document balances.
What ships with it
2 files 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.
- 3d ago First seen · 121 lines · 71 tokens per session scan A 1157de27d5ab
transcript-to-pdf is a skill published in the GitHub repository Elumenotion/GuideAnts (57 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,128 once invoked, about $0.0004 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-03.
Other skills, from other repositories
data-export
Generates data export/import infrastructure for JSON, CSV, PDF formats with GDPR data portability, share sheet integration, and file import. Use when user wants data export functionality, CSV/JSON/PDF export, GDPR compliance data portability, import from files, or share sheet for data.
documentation-standards
Apply markdown documentation standards optimized for both LLM consumption and Pandoc PDF generation. Use whenever the user is writing or.
pandoc-pdf-generation
PDF generation from markdown via Pandoc/XeLaTeX. TRIGGERS - markdown for PDF, print document, pandoc.
terminal-print
Print iTerm2 terminal output to network printer. Also documents AirPrint blank-page workaround for HP LaserJet Pro MFP 3101/3108 family. TRIGGERS - print terminal, terminal PDF, print session output, AirPrint blank page, printer prints blank, lpr no output, HP LaserJet driverless blank, IPP-Everywhere blank page.
latex-build
LaTeX builds with latexmk and live preview. TRIGGERS - latexmk, LaTeX build, live preview, compilation.
document-skills
Professional document creation, editing, and analysis for Office formats (docx, pdf, pptx, xlsx). Use when working with Word documents, PDFs, PowerPoint presentations, or Excel spreadsheets.