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 skills add sinch/sinch-plugins --skill sinch-api-messages-listgit 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-messages-list)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-api-messages-list"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-api-messages-list.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.1 | $0.00016 | $0.00610 |
| Opus 5 | $0.00008 | $0.00305 |
| Sonnet 5 | $0.00003 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
sinch-api-messages-list 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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
List Messages
List or retrieve messages for a conversation or contact using the Sinch Conversation API. Supports filtering by channel, contact, conversation, and pagination.
IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.
Input
--channel/-c: Channel filter (SMS, RCS, WHATSAPP) - optional--contact-id/-C: Contact ID to list messages for - optional--conversation-id/-i: Conversation ID - optional--page-size/-n: Number of results (default 20) - optional--page-token/-p: Pagination token from previous response - optional--format/-f: Output format (table or json) - optional, default table
Arguments: $ARGUMENTS
Instructions
Execute these steps directly - do not write code or scripts:
-
If $ARGUMENTS empty: ask if user wants to list by contact, conversation, or channel; ask for IDs if needed. Otherwise parse.
-
Validate: optional --channel, --contact-id, --conversation-id, --page-size (number), --page-token, --format (table|json).
-
Try MCP tool for listing messages if available (e.g. list-messages). On success format and display result, then exit.
-
If MCP not available: get CONVERSATION_* env vars. If missing, report "Sinch API is not configured."
-
Use Conversation API list messages endpoint(s): e.g. GET /v1/projects/{projectId}/messages or equivalent with query params (contact_id, conversation_id, channel, page_size, page_token). Use OAuth2 Bearer token.
-
Format response: table (columns: id, direction, channel, state, timestamp, snippet) or raw JSON. Display pagination token if present.
-
On success display "✅ Messages listed" with count. Handle errors (404, 403, etc.) with clear messages.
-
Handle all errors gracefully.
Examples
/sinch-api-messages-list --channel=SMS --page-size=10
/sinch-api-messages-list --contact-id=CONTACT_ID --format=json
/sinch-api-messages-list -c WHATSAPP -n 20 -f table
API Reference
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.
- 6d ago First seen · 61 lines · 16 tokens per session scan A abd8bfac4e65
sinch-api-messages-list is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 24d ago), licensed Apache-2.0. It adds 16 tokens to every session and 610 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
wraps-workflows
Build email and SMS automation workflows using the @wraps.dev/client TypeScript DSL. Covers triggers, steps, branching, cascades, and the full defineWorkflow API.
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
wikipedia
Search and read Wikipedia via x wkp — MediaWiki API, no API key, zero install; query, extract, suggest, and DDG route in one module. Load for wiki, wikipedia, encyclopedia lookup, article summary.
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.