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/markmhendrickson/ateles/stream-transcriptnpx skills add markmhendrickson/ateles --skill stream-transcriptgit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/markmhendrickson/ateles/stream-transcript)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/stream-transcript"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/stream-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 | $0.00109 | $0.05812 |
| Opus 5 | $0.00055 | $0.02906 |
| Sonnet 5 | $0.00022 | $0.01162 |
| Haiku 4.5 | $0.00011 | $0.00581 |
Grade A, and why
stream-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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream transcript
Feed a live meeting transcript into the current session while the meeting is still happening, so the agent holds the conversation as context rather than reading it afterwards.
This is the live, advisory half of meeting capture. The authoritative
half is unchanged and still owned by Tyto + analyze-meeting:
full-file, diarized, stored in Neotoma, reconciled against the graph.
Relationship to the rest of the pipeline
| Live stream (this skill) | Post-hoc (Tyto → analyze-meeting) |
|
|---|---|---|
| When | While recording | After the file settles |
| Engine | Whisper only, no diarization | Best available, diarized |
| Boundaries | Arbitrary N-second cuts | Whole file |
| Speakers | System track only — not the operator's mic | Both tracks, merged |
| Neotoma | Nothing durable | Authoritative entities |
| Purpose | Orient the agent mid-meeting | Metabolize the meeting |
Live chunks are provisional by construction. They are cut mid-sentence, they garble non-speech, and they never see the operator's own voice. Treat every live claim as something the authoritative pass will restate better.
Recorder control: detect only
This skill does not start or stop Audio Hijack. Audio Hijack 4 exposes
scripted control via App Intents (AH4RunScriptIntent), and this machine already
has a Tyto session plus start_tyto_* / stop_tyto_test scripts and Shortcuts
— but as of 2026-08-28 all three Shortcuts fail with "An unknown error occurred"
and change no recording state, likely because scripted control requires
confirmation (confirmAH4RunScript:completion:). Until that is resolved, the
operator starts and stops the recorder; this skill detects what is running.
Note: shortcuts run exits 0 even when the shortcut fails. Never trust its
exit code — parse its output.
/stream-transcript start
1. Detect a growing recording
cd "$ATELES_REPO" && execution/venv/bin/python - <<'PY'
import sys; sys.path.insert(0, "execution/scripts")
import live_transcript_tail as lt
rec = lt.find_growing_recording(lt.DEFAULT_DIR)
print(rec if rec else "NONE")
PY
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 · 490 lines · 109 tokens per session scan A 1d595fa0313e
stream-transcript is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 5,812 once invoked, about $0.0005 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
matryca-logseq-io
Choose safe direct-file versus Local HTTP API access for Logseq. Use when changing graph reads, writes, background indexing, live Logseq integration, authentication, or JSON-RPC communication.
simplicio-loop
Unified public entrypoint for Simplicio's body-of-work orchestration: core + loop in one command. Use when the user types /simplicio-loop, says "ralph loop", "keep iterating until done", "finish all open issues", or asks to drain a queue of work autonomously. Runtime-agnostic: binds a real stop-hook where the host…
leader-explore-plan-implement
Orchestrate the full lifecycle of delegated technical work: explore the problem space, author an implementation plan, then coordinate implementation across team members. This pipeline composes leaf skills (systematic-exploration, implementation-plan-authoring) into a leader workflow with explicit phase gates…
life-automation-audit
Use this as an on-demand long prompt. Do not paste it into SOUL.md / PRINCIPLES.md / AGENTS.md. When the user asks to audit their life for automation opportunities, load and follow this prompt.
visited-tracker-tools
Use visited-tracker to record file coverage, avoid duplicate work, and leave handoff notes that persist across conversations.
discord
Control Discord via the discord tool: manage messages, reactions, polls, channels, and bot presence.