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.
git 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/commands/sinch/sinch-plugins/sinch-help)<a href="https://agentmods.dev/commands/sinch/sinch-plugins/sinch-help"><img src="https://agentmods.dev/badge/commands/sinch/sinch-plugins/sinch-help/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sinch/sinch-plugins/sinch-help"><img src="https://agentmods.dev/badge/commands/sinch/sinch-plugins/sinch-help.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.01328 |
| Opus 5.5 | $0.00006 | $0.00531 |
| Sonnet 5.5 | $0.00003 | $0.00266 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade B, and why
sinch-help scanned grade B with 1 finding 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 12d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
~/.claude/settings.json How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sinch Conversation API Setup
Configure the required environment variables to enable the Sinch Conversation API MCP server in Claude Code.
Overview
This plugin uses the Sinch Conversation API MCP server (defined in .mcp.json) to send and receive messages via SMS and RCS channels. It supports multiple message types (text, media, location, choice, template), batch messaging (up to 1000 recipients), template management, and channel fallback.
For more details about the underlying MCP server and tools, see Sinch MCP Server
Required Environment Variables
You need to obtain and configure the following 5 variables:
PROJECT_ID- Your Sinch project IDKEY_ID- Your API key IDKEY_SECRET- Your API key secretCONVERSATION_REGION- Your Sinch region (e.g.,us,eu,br)CONVERSATION_APP_ID- Your Conversation app ID
Get Your Sinch Credentials
- Create a Sinch Build account (see here for instructions on setting up an account).
- Enable the product in the dashboard: Conversation API.
- Generate an access key in the Sinch Build Dashboard. If you need help, review our Community article on access key creation.
Configuration Steps
1. Open Claude Code Settings
On macOS, the settings file is located at:
~/.claude/settings.json
You can open it by:
- Using a text editor:
code ~/.claude/settings.jsonoropen -a TextEdit ~/.claude/settings.json - Using Finder: Press
Cmd+Shift+Gand paste~/.claude/settings.json
2. Add Environment Variables
Add or update the env section in your settings.json:
{
"env": {
"PROJECT_ID": "your-project-id-here",
"KEY_ID": "your-key-id-here",
"KEY_SECRET": "your-key-secret-here",
"CONVERSATION_REGION": "your-app-region (e.g., us, eu, br)",
"CONVERSATION_APP_ID": "your-app-id-here"
}
}
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.
- 12d ago Changed b2167c4c647f
- 1mo ago First seen · 134 lines · 14 tokens per session scan B c22fa8851d29
sinch-help is a command published in the GitHub repository sinch/sinch-plugins (6 stars, last pushed 12d ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,328 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
api-docs.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
maestro-fork
Create or sync session worktree for parallel dev.
maestro-guard
Manage editing boundary restrictions.
maestro-spec
A command for recording project rules and constraints, such as coding standards, architecture decisions, or quality requirements. It turns a plain-language statement into a recorded specification.
maestro-issue
A command for managing issues, which are tracked problems or tasks, through their full lifecycle.
checklist
Generate a custom checklist for the current feature based on user requirements.