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 DavidROliverBA/ArchitectKB --skill voice-meetinggit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/voice-meeting)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/voice-meeting"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/voice-meeting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/voice-meeting"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/voice-meeting.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00869 |
| Opus 5 | $0.00005 | $0.00434 |
| Sonnet 5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
voice-meeting 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 9d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/voice-meeting
Record a meeting using voice capture and automatically create a meeting note with transcript.
Usage
/voice-meeting start <title>
/voice-meeting start <title> for <project>
/voice-meeting stop
/voice-meeting status
Examples
/voice-meeting start Weekly Team Sync
/voice-meeting start Architecture Review for Project - Alpha
/voice-meeting stop
/voice-meeting status
Prerequisites
Before using this skill, ensure:
- The Inworld voice-agent server is running at
ws://localhost:4000 - Start it with:
cd ~/Documents/GitHub/claude-voice && npm run start:server - Microphone permissions are granted
Instructions
For start action:
-
Parse the command for:
- title: Meeting name (required)
- project: Project mentioned after "for" (optional)
-
Use the
voice_listen_continuousMCP tool with action "start":mcp__voice-mcp__voice_listen_continuous({ action: "start", title: "<meeting title>" }) -
Store the session_id returned for later use
-
Inform the user:
- Recording has started
- Remind them to say
/voice-meeting stopwhen finished - Mention they can check status with
/voice-meeting status
For stop action:
-
Use the
voice_listen_continuousMCP tool with action "stop":mcp__voice-mcp__voice_listen_continuous({ action: "stop" }) -
Retrieve the full transcript and segments from the response
-
Generate filename:
Meeting - YYYY-MM-DD {{title}}.md -
Create the meeting note in Meetings/ folder:
---
type: Meeting
title: { { title } }
created: { { DATE } }
modified: { { DATE } }
tags: [voice-recorded]
date: "{{DATE}}"
project: { { project_link or null } }
attendees: []
summary: { { AI-generated summary of transcript } }
collections: null
recordingSession: { { session_id } }
duration: { { duration_ms formatted as HH:MM:SS } }
wordCount: { { word_count } }
---
# {{title}}
## Recording Info
- **Session ID**: {{session_id}}
- **Duration**: {{duration formatted}}
- **Word Count**: {{word_count}}
## Attendees
(To be filled in)
## Transcript
{{full_transcript}}
## AI Summary
{{Generate 3-5 bullet point summary of the meeting}}
## Action Items
{{Extract any action items mentioned in transcript, or leave template:}}
- [ ]
## Decisions Made
## {{Extract any decisions mentioned, or leave template:}}
## Follow-up
-
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.
- 9d ago First seen · 163 lines · 9 tokens per session scan A 31e9f459636b
voice-meeting is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 869 once invoked, about $0.0000 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.