Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSmokeDev/taskchad-os/master/.claude/skills/talk-mode-setup/SKILL.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/talk-mode-setup)<a href="https://agentmods.dev/skills/thesmokedev/taskchad-os/talk-mode-setup"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/talk-mode-setup.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.00000 | $0.03511 |
| Opus 5 | $0.00000 | $0.01755 |
| Sonnet 5 | $0.00000 | $0.00702 |
| Haiku 4.5 | $0.00000 | $0.00351 |
Grade A, and why
talk-mode-setup 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 4d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Talk Mode Setup
Adds voice to a framework install that is already running. This does not bootstrap a second brain, it gives an existing one a mouth and ears.
For the architecture, the receive-pipeline story, and the design notes, send the
user to docs/talk-mode-showcase.md. Do not restate it here.
Rules of engagement
This skill is interactive. The user drives.
- Reads and checks are free. Run the preflight, inspect
.env, check the OS, look for the venv. Never ask permission to look. - Every write is gated. Before touching
.env, creating a venv, or starting a service, show exactly what you are about to do and get an explicit pick viaAskUserQuestion(or the running provider's question tool). - Detect, then ask only what is missing. Somebody half set up must not re-answer solved questions. Skip any step the preflight already reports green.
- One question per real decision, with concrete options. Never a freeform "ok?".
Step 1. Detect (no questions yet)
cd .claude/scripts
uv run python ../skills/talk-mode-setup/scripts/preflight.py --json
The JSON gives you everything you need to branch:
| Field | Use it to |
|---|---|
source |
Which credential currently wins: codex-oauth, env, or configured. |
codexAvailable |
Whether a Codex ChatGPT login exists at all. |
preferCodex |
Whether TALK_PREFER_CODEX_OAUTH already pins voice to the subscription. If true, skip the billing question. |
talkKeySet / envKeySet |
Which API keys are set. Drives the metering warning. |
Discord bot token check |
Whether the Discord surface is even possible. |
Discord voice sidecar check |
Whether the venv is built, and whether this OS can run it. |
| port checks | Whether the services are already up. |
Also record the OS. sys.platform is enough.
Report the findings back in one short block before asking anything. The user should see the current state before making choices.
What ships with it
4 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.
- 4d ago First seen · 301 lines · 0 tokens per session scan A 404b93713bcb
talk-mode-setup is a skill published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,511 tokens. 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
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
sunday-review
Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed…
cierre-de-llamada
Use when a SALES or CLIENT call just ended and the follow-up needs to be produced from its transcript. Triggers: /cierre, "close out this call", "acabo de tener una llamada", "arma el seguimiento", "what's the follow-up on this call", "qué sigue con este cliente", or the user pastes a sales-call transcript. Produces…