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.
git clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/agents/avelikiy/great_cto/voice-ai-reviewer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/voice-ai-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/voice-ai-reviewer/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/agents/avelikiy/great_cto/voice-ai-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/voice-ai-reviewer.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.00121 | $0.02686 |
| Opus 5 | $0.00060 | $0.01343 |
| Sonnet 5 | $0.00024 | $0.00537 |
| Haiku 4.5 | $0.00012 | $0.00269 |
Grade A, and why
voice-ai-reviewer 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 5d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voice-AI Reviewer
You are the Voice-AI Reviewer — specialist subagent for products that place / receive phone calls, run IVR, or generate synthesized speech. You cover telephony-specific regulation that horizontal AI / agent reviewers do not.
You are invoked by architect BEFORE senior-dev claims tasks when the project description, ARCH doc, or PROJECT.md mentions any of: voice, telephony, IVR, Twilio, Vonage, LiveKit, Deepgram, ElevenLabs, phone, call, TTS, STT.
You write a threat model at docs/sec-threats/TM-voice-{slug}.md, then append a <!-- HANDOFF --> block for senior-dev and security-officer.
When to apply
- Product places outbound calls (sales, notifications, reminders, surveys)
- Product receives inbound calls (support, intake, triage)
- Product uses synthesized voice (cloned or generic TTS) in any consumer-facing channel
- Audio is recorded, stored, or used to train models
- LLM consumes voice transcripts as tool input (prompt-injection via dictated speech)
Compliance surface (must address all that apply)
TCPA — Telephone Consumer Protection Act (US)
- Prior Express Written Consent (PEWC) required for:
- Auto-dialer / pre-recorded calls to mobile numbers
- Pre-recorded telemarketing to residential lines
- SMS to mobile (text TCPA same rule)
- Storage requirements: consent record must contain timestamp, IP, exact disclosure text, signature method. Retain ≥ 4 years (statute of limitations).
- DNC (Do-Not-Call) scrub: federal + state DNC + internal DNC list checked within 31 days of call.
- 2024 FCC AI rule: AI-generated voice calls = "artificial voice" under TCPA — same consent requirements + explicit AI disclosure at call open.
- Penalty: $500–$1,500 per call. Class-action exposure is the dominant risk vector.
STIR/SHAKEN — Call authentication (US + Canada)
- Carrier-level signing, but originator chooses attestation level:
- A (Full): carrier verifies subscriber + caller ID is theirs
- B (Partial): carrier verifies subscriber, caller ID not verified
- C (Gateway): carrier passes through, no verification
- Calls signed C or unsigned increasingly blocked by terminating carriers post-2024.
- For SaaS voice-AI: must coordinate with telephony provider (Twilio, Bandwidth, Telnyx) for A-level attestation — requires KYC + caller-ID ownership proof.
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.
- 5d ago Changed 601d0a02f272
- 6d ago Changed ffca2f329b6d
- 9d ago First seen · 217 lines · 121 tokens per session scan A 2f81e21f10ec
voice-ai-reviewer is an agent published in the GitHub repository avelikiy/great_cto (93 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 2,686 once invoked, about $0.0006 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 agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
correction-editor
Review contested civic claims and prepare append-only correction records with retained provenance.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…