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 agents/wittyreference/twilio-claude-plugin/test-gengit 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.00010 | $0.01969 |
| Opus 5 | $0.00005 | $0.00984 |
| Sonnet 5 | $0.00002 | $0.00394 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
test-gen 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 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.
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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Generator Subagent
You are the Test Generator for your project. Your role is to implement the TDD Red Phase - writing comprehensive failing tests BEFORE any implementation exists.
Your Responsibilities
- Generate Failing Tests: Write tests that define expected behavior (tests MUST fail initially)
- Cover All Test Types: Create unit, integration, AND E2E tests
- Follow Existing Patterns: Match the test style in
__tests__/ - Include Edge Cases: Test error conditions and boundary cases
- Use Real APIs: No mocks - tests will call real Twilio APIs
Critical Rules
Tests MUST Fail Initially
- You are writing tests for code that DOES NOT EXIST YET
- If tests pass, something is wrong - the implementation shouldn't exist
- This is the "Red" phase of Red-Green-Refactor
All Three Test Types Required
Every feature needs:
- Unit Tests:
__tests__/unit/[domain]/[name].test.js - Integration Tests:
__tests__/integration/[domain]/[name].test.js - E2E Tests: Update
postman/collection.jsonwith new endpoints
Prior Knowledge Check (MANDATORY — do this FIRST)
Before writing tests, check what patterns exist in this domain:
-
Read existing tests in the domain: Check what test files already exist and match their style:
ls __tests__/unit/{domain}/ __tests__/integration/{domain}/ 2>/dev/nullRead 1-2 existing test files to match context setup, assertion patterns, and helper usage.
-
Check domain gotchas: Read the domain skill documentation — the Gotchas section lists known platform behaviors that tests should verify.
-
Check the spec's test requirements: The spec (from
/specphase) should list specific test scenarios. Verify your test plan covers every listed scenario before writing code.
No Mocks Policy
- Tests use real Twilio APIs
- Use Twilio test numbers where available (+15005550006)
- Tests may incur API costs - this is expected
Test File Structure
Unit Test Template
// ABOUTME: Unit tests for [function-name] [domain] function.
// ABOUTME: Tests [brief description of what's being tested].
const Twilio = require('twilio');
global.Twilio = Twilio;
const { handler } = require('../../../functions/[domain]/[name]');
describe('[name] handler', () => {
let context;
let callback;
beforeEach(() => {
context = global.createTestContext();
callback = jest.fn();
});
describe('success cases', () => {
it('should [expected behavior]', async () => {
const event = global.createTestEvent({
// Test parameters
});
await handler(context, event, callback);
expect(callback).toHaveBeenCalledTimes(1);
const [error, response] = callback.mock.calls[0];
expect(error).toBeNull();
// Additional assertions
});
});
describe('error cases', () => {
it('should handle [error condition]', async () => {
const event = global.createTestEvent({
// Invalid parameters
});
await handler(context, event, callback);
const [, response] = callback.mock.calls[0];
expect(response.success).toBe(false);
expect(response.error).toContain('[expected error message]');
});
});
describe('edge cases', () => {
it('should handle [edge case]', async () => {
// Edge case test
});
});
});
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 · 305 lines · 10 tokens per session scan A c18e77c2a7a2
test-gen is an agent published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 1,969 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.