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-webhooks-createnpx skills add sinch/sinch-plugins --skill sinch-api-webhooks-creategit 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-webhooks-create)<a href="https://agentmods.dev/skills/sinch/sinch-plugins/sinch-api-webhooks-create"><img src="https://agentmods.dev/badge/skills/sinch/sinch-plugins/sinch-api-webhooks-create.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.00017 | $0.01277 |
| Opus 5 | $0.00009 | $0.00639 |
| Sonnet 5 | $0.00003 | $0.00255 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
sinch-api-webhooks-create 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Webhook
Create a new webhook to receive real-time notifications about message events and other activities from Sinch Conversation API.
IMPORTANT: Execute this command directly. Do NOT generate script files. Do NOT create Python/JavaScript files. Perform the API call immediately using the instructions below.
Input
--target/-t: Target URL where webhook events will be sent (required)--triggers/-T: Comma-separated list of event triggers (required)--secret/-s: Secret token for validating webhook requests (optional)
Arguments: $ARGUMENTS
Instructions
Execute these steps directly - do not write code or scripts:
-
Check if $ARGUMENTS is empty or only contains the command name:
- If empty or no meaningful arguments provided, enter interactive mode:
- Ask: "🌐 What is the target webhook URL? (must be HTTPS)"
- Ask: "🔔 Which triggers do you want? (comma-separated, or type 'list' to see available triggers)"
- If user types 'list', show the Available Triggers section, then ask again
- Ask: "🔐 Do you want to set a custom secret? (optional, press Enter to auto-generate)"
- Use the provided answers as the arguments for the following steps
- If arguments are provided, proceed directly to step 1
- If empty or no meaningful arguments provided, enter interactive mode:
-
Parse and validate arguments from $ARGUMENTS or interactive input:
- Validate that
--targetis provided and is a valid HTTPS URL - Validate that
--triggersis provided and non-empty - Parse triggers as a comma-separated list
- Validate each trigger against the available trigger types
- If
--secretis not provided, generate a random secret
- Validate that
-
Try to call
mcp__sinch__sinch-mcp-configurationto get the current configuration. -
If MCP is NOT available, retrieve configuration from environment variables:
- CONVERSATION_PROJECT_ID
- CONVERSATION_REGION
- CONVERSATION_APP_ID
- CONVERSATION_KEY_ID
- CONVERSATION_KEY_SECRET
- If any are missing, report: "Sinch API is not configured. Please set the required environment variables."
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 · 139 lines · 17 tokens per session scan A 1f1f651440f0
sinch-api-webhooks-create is a skill published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 21d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,277 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…