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/djrhails/dotfiles/process-transcriptnpx skills add DJRHails/dotfiles --skill process-transcriptgit clone --depth 1 https://github.com/DJRHails/dotfilesWhat 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 | $0.00063 | $0.01262 |
| Opus 5 | $0.00032 | $0.00631 |
| Sonnet 5 | $0.00013 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
process-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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Transcript Skill
Transform verbose video/podcast transcripts into comprehensive, structured notes that follow the knowledge base style guide principles: density over verbosity, practical over theoretical, direct communication.
Instructions
1. Read the Transcript
For large transcripts (>25,000 tokens), use Task tool with general-purpose agent:
Use Task tool:
- subagent_type: "general-purpose"
- description: "Extract key insights from transcript"
- prompt: "Read the transcript at [PATH] and extract:
1. Main themes and concepts discussed
2. Specific advice, rules, or frameworks
3. Key examples and anecdotes
4. Practical tips for different scenarios
5. Important quotes or memorable phrases
6. Any mental models or frameworks mentioned
Structure findings with clear sections and bullet points. Focus on actionable advice and concrete examples."
2. Extract Compelling Quotes
Run second agent task focused on quotable moments:
Use Task tool:
- subagent_type: "general-purpose"
- description: "Extract compelling quotes from transcript"
- prompt: "Read the transcript at [PATH] and extract the most compelling, memorable, and quotable statements. Look for:
1. Funny or witty observations
2. Strong opinions stated colorfully
3. Memorable phrases or turns of phrase
4. Contrarian or surprising takes
5. Practical wisdom stated memorably
6. Self-aware or self-deprecating moments
Extract exact quotes (verbatim) with context. Organize by theme."
3. Structure the Notes
Replace the existing summary with structured sections following this pattern:
Opening sections (choose based on content):
- Core Philosophy / Main Thesis
- Key Concepts
- Overview
Body sections (organize by topic):
- Group related advice together
- Use descriptive H2 headers (
##) - Subsections with H3 (
###) where needed
Common section types:
- Mental models and frameworks
- Practical advice by scenario
- Examples and case studies
- Personal context about speaker
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 · 178 lines · 63 tokens per session scan A 3f721b38c3ff
process-transcript is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 1,262 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-08-31.
Other skills, from other repositories
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
dustoff
Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives…