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/sinch/sinch-plugins/sinch-api-verification-startnpx skills add sinch/sinch-plugins --skill sinch-api-verification-startgit clone --depth 1 https://github.com/sinch/sinch-pluginsWrote 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/sinch/sinch-plugins/sinch-api-verification-start)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-api-verification-start"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-api-verification-start.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00494 |
| Opus 5 | $0.00013 | $0.00247 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
sinch-api-verification-start 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 4d 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.
What it actually says
Start Phone Verification
Start a phone number verification using the Sinch Verification API. Supports SMS (PIN code), Flashcall (missed call), or Callout (voice TTS). Uses Application Key + Secret.
IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.
Input
--to/-t: Phone number to verify (E.164) - required--method/-m: Verification method: sms, flashcall, or callout - required (default sms)
Arguments: $ARGUMENTS
Instructions
Execute these steps directly - do not write code or scripts:
-
If $ARGUMENTS empty: ask for phone number and method (sms, flashcall, callout). Otherwise parse.
-
Validate: --to (E.164), --method (sms | flashcall | callout). Normalize method to lowercase.
-
Get VERIFICATION_APPLICATION_KEY and VERIFICATION_APPLICATION_SECRET from env (or shared Voice/Verification app credentials if documented). Verification API uses Application Key/Secret. If missing, report "Verification API is not configured. Set application key and secret for Verification app."
-
Request body: identity { type: "number", endpoint: "+E164" }, method.
-
POST https://verification.api.sinch.com/verification/v1/verifications with Basic Auth (application_key:application_secret), Content-Type application/json.
-
On success: "✅ Verification started" with verification ID. Tell user to share the code with the end user (SMS) or that Flashcall/Callout was triggered. Handle 400, 401, 429 with clear messages.
-
Handle all errors gracefully.
Examples
/sinch-api-verification-start --to=+14155551234 --method=sms
/sinch-api-verification-start -t +14155551234 -m callout
API Reference
- Base URL: https://verification.api.sinch.com/verification/v1
- Endpoint: POST /verifications
- Auth: Basic (application_key:application_secret)
- Documentation: https://developers.sinch.com/docs/verification/
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.
- 4d ago First seen · 50 lines · 25 tokens per session scan A 4ef24561154b
sinch-api-verification-start is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 22d ago), licensed Apache-2.0. It adds 25 tokens to every session and 494 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 skills, from other repositories
agentrq
Learn creating, scheduling tasks, workspaces, and collaborating with human operators on the AgentRQ platform. Lead colony of AI agents using AgentRQ MCP tools.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
test-repo
Use this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and checkpoint creation work correctly.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
model-update
新增或更新 CCX 项目中的模型注册技能。适用于 Claude 与非 Claude 模型，覆盖能力表、路由白名单、基准映射、代码生成与验证。.
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.