Borrowing it
Nothing to install: this file belongs to vendelieu/telegram-bot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vendelieu/telegram-bot/master/.cursor/skills/bot-user/build-reply-keyboard/SKILL.mdgit clone --depth 1 https://github.com/vendelieu/telegram-botWrote 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/vendelieu/telegram-bot/build-reply-keyboard)<a href="https://agentmods.dev/skills/vendelieu/telegram-bot/build-reply-keyboard"><img src="https://agentmods.dev/badge/skills/vendelieu/telegram-bot/build-reply-keyboard.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00603 |
| Opus 5 | $0.00022 | $0.00302 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
build-reply-keyboard 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Reply Keyboard
Quick Start
Use replyKeyboardMarkup { } or replyKeyboardMarkup(block). Attach via markup() or replyKeyboardMarkup { } on send actions.
message("Choose an option:")
.replyKeyboardMarkup {
+"Option A"
+"Option B"
newLine()
"Share contact" requestContact true
options { resizeKeyboard = true; oneTimeKeyboard = true }
}
.send(user, bot)
Simple Buttons
Use unary plus to add plain text buttons:
+"Button 1"
+"Button 2"
newLine()
+"Next row"
Special Buttons
| Type | Syntax | Availability |
|---|---|---|
| Request contact | "Share contact" requestContact true |
Private chats only |
| Request location | "Share location" requestLocation true |
Private chats only |
| Request user | "Select user" requestUser KeyboardButtonRequestUsers(...) |
Private chats only |
| Request chat | "Select chat" requestChat KeyboardButtonRequestChat(...) |
Private chats only |
| Request poll | "Create poll" requestPoll KeyboardButtonPollType(...) |
Private chats only |
| Web App | "Open app" webApp "https://..." |
Private chats only |
Options
Configure via options { }:
resizeKeyboard = true— keyboard resizes to fit screenoneTimeKeyboard = true— keyboard hides after one useinputFieldPlaceholder = "Type here..."— placeholder in input field (1-64 chars)selective = true— show only to @mentioned users or reply targetisPersistent = true— keyboard stays visible (for oneTimeKeyboard)
Rows
Use newLine() or br() to start a new row, same as inline keyboards.
Removing the Keyboard
When done, send a message with replyKeyboardRemove():
message("Keyboard removed")
.replyKeyboardRemove()
.send(user, bot)
Or replyKeyboardRemove(selective = true) for selective removal.
Reference
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 · 77 lines · 0 tokens per session scan A 9c376b74b9fd
build-reply-keyboard is a skill published in the GitHub repository vendelieu/telegram-bot (248 stars, last pushed 11d ago), licensed Apache-2.0. It adds 44 tokens to every session and 603 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-30.
Other skills, from other repositories
react-email
Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and…
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…
writing-clearly-and-concisely
Apply whenever writing content a human will read — emails, documents, reports, documentation, messages, UI copy, commit messages, explanations, or any other prose. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
sceneview-web
Build 3D and WebXR (AR/VR) experiences in the browser with SceneView for Web — Filament.js (WebGL2/WASM) wrapped in a Kotlin/JS DSL and a plain-JavaScript API on window.sceneview. Use whenever the user asks for "3D in the browser", "a web model viewer", "WebXR AR/VR", or any browser 3D/AR app where the dependency is…
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
starter-dashboard
Scaffold a local Next.js Alpaca dashboard using the published @alpacahq/alpaca-trade-api SDK for paper Trading API and Market Data API workflows. Use when the user asks for starter-dashboard, a starter Alpaca dashboard, a local Trading API demo, a Market Data API dashboard, or a greenfield Next.js Alpaca SDK prototype.