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/Harddiikk/dograh-voicelink-pluginWrote 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/harddiikk/dograh-voicelink-plugin/voicelink-configure)<a href="https://agentmods.dev/commands/harddiikk/dograh-voicelink-plugin/voicelink-configure"><img src="https://agentmods.dev/badge/commands/harddiikk/dograh-voicelink-plugin/voicelink-configure/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/harddiikk/dograh-voicelink-plugin/voicelink-configure"><img src="https://agentmods.dev/badge/commands/harddiikk/dograh-voicelink-plugin/voicelink-configure.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.00038 | $0.00643 |
| Opus 5 | $0.00019 | $0.00321 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
voicelink-configure 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/voicelink-configure
Configure a VoiceLink-enabled Dograh. Assumes the overlay is installed and verified
(/voicelink-install, /voicelink-verify). Follow references/telephony-card-guide.md
and references/single-wss-url.md.
1. The single WSS URL (print it for the user)
Derive from their public origin and show both forms:
Inbound (paste in VoiceLink portal): wss://<host>/api/v1/telephony/ws
Outbound (Dograh sends automatically): wss://<host>/api/v1/telephony/ws/{workflow_id}/{organization_id}/{workflow_run_id}
scripts/verify.sh <base-url> prints these exactly. The host = BACKEND_API_ENDPOINT
with https→wss. This is the only URL VoiceLink needs — one URL, both directions.
2. Settings → Telephony card (in the Dograh UI)
Walk the user through Settings → Telephony → Add telephony configuration → VoiceLink. The card is credentials only:
| Field | Value | Note |
|---|---|---|
| Username + Password | VoiceLink login | Lets tokens auto-refresh on 401 |
| Bearer Token | (alternative to user/pass) | Static; no auto-refresh |
No API base or DID field: api_base defaults to https://app.voicelink.co.in/api in the
schema. DIDs are added as phone-number rows in the next step.
Save (requires either bearer_token OR username+password). Then on the config detail page, add each DID — this is required for both directions:
- Inbound: bind the DID to an inbound workflow (creates the
telephony_phone_numbersrow the inbound handler routes against). - Outbound: the telephony factory turns the active rows into the provider's
from_numbers; the campaign dispatcher uses one as the caller id. VoiceLink'sadd_leadrejects a call with nodid_number, so at least one active DID must exist.
3. VoiceLink portal
In VoiceLink's own panel, set the inbound bot/stream URL to the bare
wss://<host>/api/v1/telephony/ws. Outbound needs no portal config.
4. Sanity
- Outbound
customer_numbermust be a bare 10-digit local number (no country code), or the carrier rejects with Q.850 cause 38. - Place a test outbound call and confirm the logged
add_leadwebsocket_url; then a test inbound call and read the logged rawstartframe (/voicelink-debugif routing misses). Confirm before declaring it done.
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 Changed · +5 lines · -4 tokens per session 15c708c9f9af
- 11d ago First seen · 49 lines · 42 tokens per session scan A 62416b2348e5
voicelink-configure is a command published in the GitHub repository Harddiikk/dograh-voicelink-plugin (9 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 643 once invoked, about $0.0002 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 commands, from other repositories
init
Initialize configurations for Supabase local development.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
api-contract-review
Review an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written…
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
build
Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.