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-sip-trunksnpx skills add sinch/sinch-plugins --skill sinch-api-sip-trunksgit 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-sip-trunks)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-api-sip-trunks"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-api-sip-trunks.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.00022 | $0.00543 |
| Opus 5 | $0.00011 | $0.00271 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
sinch-api-sip-trunks 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 5d 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
Elastic SIP Trunking — Trunks
List or create SIP trunks using the Sinch Elastic SIP Trunking API. Trunks are the top-level resource for SIP connectivity. Uses OAuth2.
IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.
Input
--action/-a: list or create - optional, default list--name/-n: Trunk name (for create) - required if action=create--host-name/-h: SIP hostname for the trunk (for create) - optional--format/-f: Output format (table or json) - optional
Arguments: $ARGUMENTS
Instructions
Execute these steps directly - do not write code or scripts:
-
If $ARGUMENTS empty: ask "List trunks or create one?" and for create get name, hostname. Otherwise parse.
-
Validate: --action (list|create), for create require --name. Get CONVERSATION_PROJECT_ID, CONVERSATION_KEY_ID, CONVERSATION_KEY_SECRET. Base: https://elastic-trunking.api.sinch.com/v1. If missing, report "Sinch API is not configured."
-
If list: GET https://elastic-trunking.api.sinch.com/v1/projects/{projectId}/trunks with OAuth2. Display table (id, name, hostName, createTime) or JSON.
-
If create: POST .../trunks with body { name, hostName }. Return trunk id and hostname. Note: use trunk-specific hostname (e.g. {trunk-hostname}.pstn.sinch.com) for SIP INVITEs, not generic trunk.pstn.sinch.com.
-
"✅ Trunks listed" or "✅ Trunk created". Handle 401, 400, 404. Handle all errors gracefully.
Examples
/sinch-api-sip-trunks
/sinch-api-sip-trunks --action=create --name="Production" --host-name=sip.example.com
API Reference
- Base URL: https://elastic-trunking.api.sinch.com/v1
- List: GET /projects/{projectId}/trunks
- Create: POST /projects/{projectId}/trunks
- Documentation: https://developers.sinch.com/docs/elastic-sip-trunking/
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.
- 5d ago First seen · 48 lines · 22 tokens per session scan A c4efbffdb737
sinch-api-sip-trunks is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 23d ago), licensed Apache-2.0. It adds 22 tokens to every session and 543 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.
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.
model-update
新增或更新 CCX 项目中的模型注册技能。适用于 Claude 与非 Claude 模型，覆盖能力表、路由白名单、基准映射、代码生成与验证。.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
happier-session-control
Manage Happier sessions and execution runs through the CLI JSON contract, and create independent Happier diagnosis sessions with explicit ownership, safe options, and fire-and-forget presentation semantics.
happier-docs
Create, update, reorganize, or review Happier internal technical documentation and published user/operator/contributor docs with evidence-backed product truth, exact release status, canonical-page ownership, human voice, minimal editing, and appropriate validation. Use whenever a change affects docs/, apps/docs/, or…