getting-started

A guide for starting a Twilio serverless project, where code runs on Twilio's infrastructure instead of a server you manage. It covers project setup, folders, credentials, and deployment.

In plain words
What is it for?
Use it to create a project from an empty directory, add serverless functions and assets, configure environment variables, and prepare the first deployment.
Why use it?
It gives a new project a defined structure and explains the configuration needed to deploy Twilio functions and static files.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/wittyreference/twilio-claude-plugin/getting-started
Any agent
npx skills add wittyreference/twilio-claude-plugin --skill getting-started
Clone the repo
git clone --depth 1 https://github.com/wittyreference/twilio-claude-plugin

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,248 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.01248
Opus 5 $0.00016 $0.00624
Sonnet 5 $0.00006 $0.00250
Haiku 4.5 $0.00003 $0.00125

Measured 2d ago against content hash c2463416bed5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

getting-started 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.

skills/getting-started/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Getting Started with Twilio Serverless

Guide for scaffolding a new Twilio serverless project from an empty directory to first deploy.

Prerequisites

  • Node.js 18+
  • Twilio account with Account SID and Auth Token
  • Twilio CLI: npm install -g twilio-cli
  • Serverless plugin: twilio plugins:install @twilio-labs/plugin-serverless

Project Setup

1. Initialize

mkdir my-twilio-project && cd my-twilio-project
npm init -y
npm install twilio @twilio-labs/serverless-runtime-types

2. Create Directory Structure

my-twilio-project/
├── functions/          # Serverless functions (auto-routed as endpoints)
│   └── hello.js        # → /hello endpoint
├── assets/             # Static files (HTML, audio, images)
├── .env                # Environment variables (never commit)
├── .twiliodeployinfo   # Deploy state (auto-generated, gitignore)
└── package.json

3. Create .env

# Required for deployment (twilio-run reads these WITHOUT the TWILIO_ prefix)
ACCOUNT_SID=ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
AUTH_TOKEN=your-auth-token

# Also set prefixed versions for your function code
TWILIO_ACCOUNT_SID=ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
TWILIO_AUTH_TOKEN=your-auth-token
TWILIO_PHONE_NUMBER=+1xxxxxxxxxx

Important: twilio-run (the serverless runtime) reads ACCOUNT_SID and AUTH_TOKEN without the TWILIO_ prefix. If you only have TWILIO_ACCOUNT_SID, deployment fails with "Missing Credentials". Add both versions.

4. Create First Function

// functions/hello.js
// ABOUTME: Simple hello world endpoint for testing deployment
// ABOUTME: Returns JSON greeting — verifies serverless runtime is working

exports.handler = function (context, event, callback) {
  const twiml = new Twilio.twiml.VoiceResponse();
  twiml.say({ voice: 'Google.en-US-Neural2-F' }, 'Hello from Twilio!');
  callback(null, twiml);
};

5. Add Scripts to package.json

{
  "scripts": {
    "start": "twilio serverless:start --live",
    "start:ngrok": "twilio serverless:start --ngrok --live --detailed-logs",
    "deploy:dev": "twilio serverless:deploy --runtime node22",
    "deploy:prod": "twilio serverless:deploy --production --runtime node22"
  }
}

Read the full file on GitHub · 160 lines

Changes

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.

  1. 2d ago First seen · 160 lines · 32 tokens per session scan A c2463416bed5

Subscribe to this mod's changes

getting-started is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 1,248 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens