Row-Bot is a local-first desktop AI assistant that combines language models with memory and tools for working across files, repositories, workflows, and communication channels. It is intended for people who want an assistant that can run locally while keeping application data on their machine.
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 skills add siddsachar/row-bot --skill developer_guidegit clone --depth 1 https://github.com/siddsachar/row-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/siddsachar/row-bot/developer_guide)<a href="https://agentmods.dev/skills/siddsachar/row-bot/developer_guide"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/developer_guide/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/skills/siddsachar/row-bot/developer_guide"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/developer_guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 59 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00024 | $0.01220 |
| Opus 5.5 | $0.00010 | $0.00488 |
| Sonnet 5.5 | $0.00005 | $0.00244 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
developer_guide 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 15d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Tool Guide
Use the Developer tools whenever the active conversation has a code folder. They are scoped to the selected workspace, follow the workspace approval mode, and keep the Developer Inspector in sync.
Default Workflow
- Start with
developer_workspace_infofor repo, branch, approval mode, execution mode, dirty state, and available context. - Use
developer_update_todosfor multi-step coding work. Keep the todo list current as you inspect, edit, test, and review. - Inspect with
developer_list_files,developer_read_file,developer_search,developer_git_status, anddeveloper_get_diffbefore changing code. - Prefer
developer_write_filefor creating or replacing full files anddeveloper_apply_patchfor precise diffs. Both record agent-owned change sets for the Inspector. - Use
developer_create_branch,developer_switch_branch,developer_commit_changes,developer_push_current_branch, anddeveloper_fast_forward_mergefor common Git workflows instead of raw shell. - Use
developer_run_detected_testfor known project test/lint commands. Usedeveloper_run_commandfor custom shell commands only when it is the right tool for the task. - If a Developer edit/test/command tool reports
execution_mode: "docker"and asandbox_pending_change_id, tell the user that the real repo has not changed yet. The Docker container persists for the workspace, but host files still change only throughdeveloper_import_sandbox_changes. - Before finishing, check
developer_get_diff, run the relevant tests, and summarize files changed, tests run, and any remaining risk.
Progress Narration
For longer work, narrate briefly in the chat before clusters of tool calls. Good examples:
- "I'll first map the repo and test surface."
- "I found the core module; now I'm adding focused tests."
- "The patch is in. I'm running the detected test command next."
Avoid silent chains of tools when the user would otherwise have no sense of what is happening.
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.
- 15d ago Changed · -1 tokens per session 9d3d67300d82
- 1mo ago First seen · 78 lines · 25 tokens per session scan A 03cbd93fcad5
developer_guide is a skill published in the GitHub repository siddsachar/row-bot (1,627 stars, last pushed today), licensed Apache-2.0. It adds 24 tokens to every session and 1,220 once invoked, about $0.0001 per session on Opus 5.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
rich-replies
Shape a reply for Telegram: headings, tables, folds, footnotes, formulas, pictures, slideshows, maps, and buttons (choice, link, copy, mini app) inside the text. Load before a structured answer, a comparison, a report in chat, or whenever you offer the user a choice or a link.
telegram-userbot
A skill for connecting to and working through the owner's personal Telegram account, rather than a Telegram bot. It can read personal chats, search messages, and send messages as the account owner after setup and consent.
rich-post
Send a rich Telegram post to ANOTHER allowlisted chat; not for the current chat reply or plain reports.
update-recovery
Use when an update leaves out owner customizations or they need restoring or merging.
agent-browser
A command-line browser for interactive websites and web apps. It can open pages, inspect clickable elements, fill forms, click buttons, take screenshots, sign in, and read pages whose content is loaded by JavaScript.
watch
A monitoring and briefing workflow that checks unread Telegram messages, email, failed checks, and failed scheduled units, then decides what needs the owner's attention. It can also explain actions such as creating a task, delaying a reminder, ignoring an item, or fixing a failure.