StenoAI is a private desktop notepad and meeting notetaker that records conversations, summarizes them, and lets users query them with local AI models. It is intended for confidential meetings in government, defence, and executive settings on Windows and macOS.
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 instructions/stenolabs/stenoai/claude-mdgit clone --depth 1 https://github.com/stenolabs/stenoaiWrote 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/instructions/stenolabs/stenoai/claude-md)<a href="https://agentmods.dev/instructions/stenolabs/stenoai/claude-md"><img src="https://agentmods.dev/badge/instructions/stenolabs/stenoai/claude-md.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.08179 | $0.08179 |
| Opus 5 | $0.04090 | $0.04090 |
| Sonnet 5 | $0.01636 | $0.01636 |
| Haiku 4.5 | $0.00818 | $0.00818 |
Grade A, and why
stenoai CLAUDE.md scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Electron main (`app/main.js`, ~6.2k lines)** owns the UI window, tray, deep-link protocol, and orchestrates everything via `ipcMain.handle(...)`. Handlers shell out to the bundled backend through `getBackendPath()` → How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Do not use excessive emojis anywhere.
Architecture
The app is a thin Electron shell over a PyInstaller-bundled Python CLI. There is no long-running Python service — every operation is a subprocess invocation.
- Electron main (
app/main.js, ~6.2k lines) owns the UI window, tray, deep-link protocol, and orchestrates everything viaipcMain.handle(...). Handlers shell out to the bundled backend throughgetBackendPath()→process.resourcesPath/stenoai/stenoai(ordist/stenoai/stenoaiin dev) usingchild_process.spawn. - Renderer (
app/renderer/) is a Vite-built React + TypeScript SPA. Runs withcontextIsolation: trueand talks to the main process exclusively through the typed bridge inapp/preload.js→ipc()(app/renderer/src/lib/ipc.ts). Built output lives atapp/renderer/dist/index.htmland is what Electron loads at runtime. - Python CLI (
simple_recorder.py, ~2.9k lines, ~60 click commands) is the single entry point bundled bystenoai.spec. Sub-modules insrc/:audio_recorder(sounddevice),transcriber(pywhispercpp),summarizer(Ollama HTTP client),ollama_manager(lifecycle of the bundledollama serve),config(JSON-backed user settings + model registry),folders,models,whisper_models. - State across CLI invocations is persisted to
recorder_state.jsonand similar small JSON files — there is no daemon. Long-running recordings are arecordsubprocess kept alive by the Electron main process. - User data lives in
~/Library/Application Support/stenoai/(recordings/,transcripts/,output/), resolved viasrc.config.get_data_dirs(). Repo-rootrecordings//transcripts//output/dirs are dev-only scratch. - Bundled binaries (
bin/): Ollama + ffmpeg, downloaded byscripts/download-ollama.sh. PyInstaller copies them intodist/stenoai/ollama/anddist/stenoai/ffmpeg. Electron then re-bundlesdist/stenoai/as anextraResource.bin/steno-diarize(macOS only) is a separate Swift/CoreML sidecar built byscripts/build-diarize-sidecar.sh— see "Speaker diarization" below. - Deep links: app registers the
stenoai://URL scheme. Handler logic is inapp/main.jsnearSHORTCUT_PROTOCOL. Used by macOS Shortcuts:stenoai://record/start?name=...andstenoai://record/stop.
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 Changed · +5 lines · +111 tokens per session 97cce418358f
- 6d ago First seen · 381 lines · 8,068 tokens per session scan A 72c8c2134102
stenoai CLAUDE.md is an instructions file published in the GitHub repository stenolabs/stenoai (1,304 stars, last pushed today), licensed MIT. It adds 8,179 tokens to every session, about $0.0409 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vexa AGENTS.md
AGENTS.md instructions for Vexa-ai/vexa, covering agents.md — the agent front door (in-repo), researching vexa? start here, driving vexa from an agent session, your issue is your prd and claiming — and say hello on discord.
vexa CLAUDE.md
Claude Code instructions for Vexa-ai/vexa, a project described as: Open-source meeting transcription API for Google Meet, Microsoft Teams & Zoom. Auto-join bots, real-time WebSocket transcripts, MCP server for AI agents. Self-host or use hosted SaaS.
Logue CLAUDE.md
Claude Code instructions for bitwize-ai/Logue, covering logue — development guidelines, project overview, running the build you just made, where documentation goes and dependencies.
apfel CLAUDE.md
Instructions for Arthur-Ficial/apfel, covering apfel - project instructions, the golden goal, core product (this is what apfel is), byproducts (useful, but not the pitch) and readme.md structure rule.
speech-swift AGENTS.md
AGENTS.md instructions for soniqo/speech-swift, covering agent instructions, communication style, workflow, running tests and benchmarks — sequential and memory-aware and git conventions.
speech-studio AGENTS.md
Instructions for soniqo/speech-studio, covering agent instructions, project, stack, sibling repos under /repos/ and build.