Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nordbyte/nordrelaynpx agentmods add skills/nordbyte/nordrelay/telegram-remoteWrote 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/nordbyte/nordrelay/telegram-remote)<a href="https://agentmods.dev/skills/nordbyte/nordrelay/telegram-remote"><img src="https://agentmods.dev/badge/skills/nordbyte/nordrelay/telegram-remote.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.00050 | $0.00314 |
| Opus 5 | $0.00025 | $0.00157 |
| Sonnet 5 | $0.00010 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
telegram-remote 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 8d 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.
What it actually says
NordRelay Remote
This Codex-side skill manages the local NordRelay process. After the runtime starts, full session control is available through the login-protected WebUI and enabled Telegram, Discord, Slack, and Matrix adapters, including trusted peer-node routing.
Use the local connector script in the plugin root. In a source checkout, the plugin root is usually:
<repo>/plugins/nordrelay
Run commands from that directory:
node scripts/nordrelay.mjs start
node scripts/nordrelay.mjs status
node scripts/nordrelay.mjs stop
node scripts/nordrelay.mjs restart
Only enabled control surfaces need credentials. TELEGRAM_BOT_TOKEN is required only when
Telegram is enabled; a WebUI-only installation does not need it. At least one NordRelay admin user
is required before the WebUI or chat adapters can control sessions. External chat identities and
channels must also be linked or enabled according to NordRelay access-control rules.
Prefer start for normal use. Use foreground only when debugging connection problems, because it keeps the current command running. If the runtime is missing, run npm install and npm run build in the repository root.
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.
- 8d ago First seen · 33 lines · 50 tokens per session scan A 2d0a34c9da11
telegram-remote is a skill published in the GitHub repository nordbyte/nordrelay (10 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 314 once invoked, about $0.0003 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
langbot-eba-adapter-dev
Build, refactor, and test LangBot platform adapters for the Event-Based Agents architecture. Use when adding or migrating Telegram, Discord, or other messaging platform adapters to the EBA adapter layout, validating unified event/message conversion, writing live adapter probes, or using standalone plugin runtime plus…
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
langbot-mcp-ops
Operate a LangBot instance through its built-in MCP (Model Context Protocol) server. Use when an AI agent needs to manage LangBot — list/create/update/delete bots, pipelines, models, knowledge bases, MCP servers, and skills — over MCP instead of raw HTTP. Covers the /mcp endpoint, API-key auth (web-UI lbk keys and the…
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…
langbot-space-ops
Browse and search the LangBot Space marketplaces (plugins, MCP servers, skills) through the Space MCP server. Use when an AI agent needs to discover LangBot extensions on space.langbot.app over MCP. Covers the /mcp endpoint, Personal Access Token (PAT) auth, the tool surface, and client configuration. Triggers on…
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.