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 summarize-transcriptgit 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/summarize-transcript)<a href="https://agentmods.dev/skills/jmagly/aiwg/summarize-transcript"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/summarize-transcript.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.00023 | $0.02190 |
| Opus 5 | $0.00012 | $0.01095 |
| Sonnet 5 | $0.00005 | $0.00438 |
| Haiku 4.5 | $0.00002 | $0.00219 |
Grade A, and why
summarize-transcript 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Transcript or Meeting
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear, actionable document.
Usage
/summarize-transcript <path-to-transcript-or-paste-content> [--style <style-preset>] [--emphasize "<guidance>"] [--avoid "<guidance>"]
Parameters
<content>: Path to transcript file OR paste content directly--style <preset>: Optional style preset (default:balanced)technical: Dense technical detail, architecture-focusedexecutive: High-level strategic, business-focusedaction-items: Task-oriented, next-steps focuseddeveloper: Code-centric, implementation detailsbalanced: Mix of strategic and technical
--emphasize "<text>": Positive guidance - what to highlight, tone to adopt--avoid "<text>": Negative guidance - what to de-emphasize or exclude
Examples
Basic Usage
/summarize-transcript meeting-notes.txt
With Style Preset
/summarize-transcript standup-transcript.md --style action-items
With Positive Guidance
/summarize-transcript design-review.txt --emphasize "Focus on security decisions and data privacy concerns"
With Negative Guidance
/summarize-transcript brainstorm-session.txt --avoid "Skip bikeshedding about naming, focus on architectural decisions"
Combined Guidance
/summarize-transcript architecture-meeting.md \
--style technical \
--emphasize "Highlight consensus mechanisms and performance trade-offs" \
--avoid "Skip discussion of tooling choices, minimize meeting logistics"
Output Structure
The command produces a structured summary following this template:
1. TL;DR Section
- Format: Emoji-prefixed bullet points (3-8 items)
- Content: Core decisions, key outcomes, critical info
- Tone: Scannable, action-oriented, high signal-to-noise
2. Detailed Breakdown
- Format: Topic-organized subsections with emoji headers
- Content: Organized by theme/domain/workstream
- Structure: Each subsection contains:
- Context/background bullets
- Decisions made
- Action items or next steps
- Open questions or risks
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 · 328 lines · 23 tokens per session scan A ee8400dfccd8
summarize-transcript is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,190 once invoked, about $0.0001 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
investor-materials
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
memstack-business-invoice-generator
Use this skill when the user says 'invoice', 'generate invoice', 'create invoice', 'bill client', 'line items', 'payment terms', or needs professional invoices with tax calculations and payment instructions. Do NOT use for contracts or financial projections.
moai-docs-generation
Documentation generation patterns for technical specs, API docs, user guides, and knowledge bases using real tools like Sphinx, MkDocs, TypeDoc, and Nextra. Use when creating docs from code, building doc sites, or automating documentation workflows.
moai-domain-html-report
Markdown-to-single-file-HTML report renderer. Six modes (status, incident, plan, explainer, financial, pr) selected by report type, crossed with three audience tiers (expert, basic, learn) derived from the active output style. The basic and learn tiers enrich the HTML with mermaid flowcharts, worked examples, and…
save-md
Saves a named source to Markdown with provenance and faithful extraction through direct export endpoints. Use when asked to "save this article", "get the markdown", "transcribe this", or "keep this source". A URL supplied as task context alone does not trigger conversion; a chat summary stays in chat.
code-handoff
Compact the current conversation into a handoff document for another agent to pick up.