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-checknpx skills add sinch/sinch-plugins --skill sinch-api-verification-checkgit 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-check)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-api-verification-check"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-api-verification-check.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.00020 | $0.00468 |
| Opus 5 | $0.00010 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
sinch-api-verification-check 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
Check / Report Verification Code
Report the verification code entered by the user to complete a Sinch Verification. Uses the verification ID returned from the start command. Uses Application Key + Secret.
IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.
Input
--id/-i: Verification ID (from start command) - required--code/-c: Code entered by the user (e.g. PIN from SMS) - required--method/-m: Method used (sms, flashcall, callout) - optional, default sms
Arguments: $ARGUMENTS
Instructions
Execute these steps directly - do not write code or scripts:
-
If $ARGUMENTS empty: ask for verification ID and the code the user entered. Otherwise parse.
-
Validate: --id (non-empty), --code (non-empty), optional --method (default sms).
-
Get Verification API application key and secret from env. If missing, report "Verification API is not configured."
-
Request body: method ("sms" or as specified), sms: { code: "" } (for SMS method). Use appropriate body for flashcall/callout if API differs.
-
PUT https://verification.api.sinch.com/verification/v1/verifications/id/{verificationId} with Basic Auth, body with method and code.
-
On success: "✅ Verification successful" or "Verification completed". On invalid code: "❌ Invalid or expired code." Handle 404, 401, 400 with clear messages.
-
Handle all errors gracefully.
Examples
/sinch-api-verification-check --id=VERIFICATION_ID --code=1234
/sinch-api-verification-check -i VERIFICATION_ID -c 5678 --method=sms
API Reference
- Endpoint: PUT /verification/v1/verifications/id/{verificationId}
- 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 · 20 tokens per session scan A 4ff43f302be4
sinch-api-verification-check is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 22d ago), licensed Apache-2.0. It adds 20 tokens to every session and 468 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 模型,覆盖能力表、路由白名单、基准映射、代码生成与验证。.
happier-session-control
Manage Happier sessions (list/status/send/wait/history/stop + execution runs) via the happier CLI JSON contract.