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/wittyreference/twilio-claude-plugin/agent-testingnpx skills add wittyreference/twilio-claude-plugin --skill agent-testinggit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWhat 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.00029 | $0.02045 |
| Opus 5 | $0.00015 | $0.01022 |
| Sonnet 5 | $0.00006 | $0.00409 |
| Haiku 4.5 | $0.00003 | $0.00204 |
Grade A, and why
agent-testing 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Busy signal / no audio | ngrok tunnel died | Verify tunnels: `curl localhost:4040/api/tunnels` | How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-to-Agent Voice Testing
Infrastructure for automated testing of Twilio voice applications using two AI agents that call each other.
Concept
Instead of manually testing voice apps by phone, use two WebSocket-based agents:
- Agent A (questioner/caller): Initiates conversation, navigates IVRs, asks questions
- Agent B (answerer/recipient): Responds to prompts, simulates customers or agents
Both connect via ConversationRelay WebSocket protocol and use an LLM (Claude, GPT, etc.) to generate natural responses based on configurable system prompts.
Architecture
┌─────────────┐ make_call ┌──────────────┐
│ Test Script │ ──────────────→ │ Twilio Voice │
└─────────────┘ │ Platform │
└──────┬───────┘
┌─────────────┴──────────────┐
Parent Leg Child Leg
(outbound-api) (inbound)
│ │
┌─────┴─────┐ ┌──────┴──────┐
│ TwiML A │ │ TwiML B │
│ <Connect> │ │ <Connect> │
│ <CR> │ │ <CR> │
└─────┬─────┘ └──────┬──────┘
│ wss:// │ wss://
┌─────┴─────┐ ┌──────┴──────┐
│ Agent A │ │ Agent B │
│ (port 8080)│ │ (port 8081) │
│ ngrok A │ │ ngrok B │
└───────────┘ └─────────────┘
Setup
1. Two WebSocket Servers
Each agent runs its own WebSocket server with a configurable system prompt:
const WebSocket = require('ws');
const Anthropic = require('@anthropic-ai/sdk');
const PORT = process.env.PORT || 8080;
const SYSTEM_PROMPT = process.env.SYSTEM_PROMPT || 'You are a helpful assistant.';
const anthropic = new Anthropic();
const wss = new WebSocket.Server({ port: PORT });
wss.on('connection', (ws) => {
const messages = [];
ws.on('message', async (data) => {
const msg = JSON.parse(data);
if (msg.type === 'prompt' && msg.last) {
messages.push({ role: 'user', content: msg.voicePrompt });
const stream = await anthropic.messages.stream({
model: 'claude-sonnet-4-20250514',
max_tokens: 256,
system: SYSTEM_PROMPT,
messages: messages,
});
let fullResponse = '';
stream.on('text', (text) => {
ws.send(JSON.stringify({ type: 'text', token: text }));
fullResponse += text;
});
await stream.finalMessage();
messages.push({ role: 'assistant', content: fullResponse });
}
});
});
console.log(`Agent listening on port ${PORT}`);
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.
- 2d ago First seen · 232 lines · 29 tokens per session scan A 9c2b46d28639
agent-testing is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 2,045 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
setup-agent-replay
Set up a local agent replay server for Raindrop Workshop. Use when the user wants Workshop to replay a captured trace against their real local agent code and tools. Creates/updates .raindrop/agents.yaml, scaffolds a language-appropriate replay server, registers the project with raindrop replay register, and verifies…
test-mcp-server
Use when testing MCP servers -- e2e tests with the sunpeak inspector, visual regression testing, live testing against real ChatGPT, multi-model evals, Playwright configuration, or scaffolding test infrastructure with "sunpeak test init". Works with any MCP server (Python, Go, TypeScript, etc.), not just sunpeak…
antigravity-sdk-e2e-dev
Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravityexecutor.py, antigravityharness.py…
harness-eval
This skill should be used when the user asks to "test the harness", "run integration tests", "validate features with real API", "test with real model calls", "run agent loop tests", "verify end-to-end", or needs to verify OpenHarness features on a real codebase with actual LLM calls.
codex-app-parity
Use only when the user explicitly mentions Codex parity, codex-app-parity, Codex.app parity, or asks to compare against the installed Codex desktop app.