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-batch-statusnpx skills add sinch/sinch-plugins --skill sinch-api-batch-statusgit 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-batch-status)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-api-batch-status"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-api-batch-status.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.00021 | $0.00560 |
| Opus 5 | $0.00010 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
sinch-api-batch-status 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 3d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Batch Job Status
Get the status of a specific batch job or list batches matching metadata using the Sinch Conversation Batch API.
IMPORTANT: Execute this command directly. Do NOT generate script files. Perform the API call immediately.
Input
--batch-id/-b: Batch ID to get status for - optional (if omitted, list batches)--metadata-key/-k: Metadata key filter when listing - optional--metadata-value/-v: Metadata value filter when listing - 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 "Do you have a batch ID to check, or list recent batches?" and get batch-id or list preference. Otherwise parse.
-
Validate: optional --batch-id, --metadata-key, --metadata-value, --format (table|json).
-
Get CONVERSATION_* env vars. Batch API base: https://{region}.conversationbatch.api.sinch.com. If missing, report "Sinch API is not configured."
-
If --batch-id provided: GET https://{region}.conversationbatch.api.sinch.com/v1/projects/{projectId}/messages/{batch_id} with OAuth2. Return batch status, counts (sent, delivered, failed), etc.
-
If listing: GET https://{region}.conversationbatch.api.sinch.com/v1/projects/{projectId}/messages?metadataKey=X&metadataValue=Y with OAuth2. Display list of batches (id, status, created, recipient count).
-
Format output as table or JSON. On success display "✅ Batch status" or "✅ Batches listed". Handle 404, 401 with clear messages.
-
Handle all errors gracefully.
Examples
/sinch-api-batch-status --batch-id=BATCH_ID
/sinch-api-batch-status
/sinch-api-batch-status --metadata-key=campaign --metadata-value=welcome --format=json
API Reference
- Base URL: https://{region}.conversationbatch.api.sinch.com
- Get batch: GET /v1/projects/{project_id}/messages/{batch_id}
- List batches: GET /v1/projects/{project_id}/messages?metadataKey=&metadataValue=
- Documentation: https://developers.sinch.com/docs/conversation/batch/
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.
- 3d ago First seen · 53 lines · 21 tokens per session scan A 3974d6bc6541
sinch-api-batch-status is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 21 tokens to every session and 560 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
triage-issue
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
git-guardrails-claude-code
Install a Claude-Code PreToolUse hook that blocks destructive git commands (push variants including force-push, hard reset, force clean, branch -D, checkout/restore overwrites) before Bash runs them. Use when the user wants git safety rails, force-push prevention, or repository-wipe protection.
agentrq
Learn creating, scheduling tasks, workspaces, and collaborating with human operators on the AgentRQ platform. Lead colony of AI agents using AgentRQ MCP tools.
duet
Two-party posture — user as director, agent as executor; every fork, tradeoff, or choice surfaced via batched AskUserQuestion with a recommended default. Use when the user invokes /duet, says "ask before" / "pair with me" / "human-in-the-loop", or for aesthetic/architectural/irreversible decisions.
explore
Read-only codebase exploration: discovery, structural reading, and emission of architecture/pattern/tooling/dependency summaries. Use to understand existing code, map files, trace function flow, locate symbols, or build pre-implementation context. Uses a staged 1/3/5 Explore-agent escalation protocol scaled to scope.…
deps-upgrade
Dependency-upgrade campaign — outdated scan, batch-by-severity, breaking-change remediation, lockfile audit. Use when CVEs require remediation, when a major upstream version lands, when stack compatibility forces a sweep, or on a scheduled (quarterly) hygiene cadence. CVE-driven bumps consume security audit findings…