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_pr_prepgit 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_pr_prep)<a href="https://agentmods.dev/skills/siddsachar/row-bot/developer_pr_prep"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/developer_pr_prep/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_pr_prep"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/developer_pr_prep.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00224 |
| Opus 5.5 | $0.00010 | $0.00090 |
| Sonnet 5.5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
developer_pr_prep 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.
What it actually says
Developer PR Prep
Use this skill when the user wants to prepare, push, or open a pull request from a conversation's code folder.
Workflow:
- Check workspace identity, branch, remote, dirty state, and GitHub CLI status.
- Recommend a feature branch when the user is still on a protected or shared branch.
- Review the diff and line counts.
- Run the relevant tests or clearly state why they were not run.
- Draft a PR title/body with summary, changed files, tests, and risk.
- Treat push and PR creation as explicit user-approved actions.
If GitHub CLI is missing or unauthenticated, explain the shortest install/auth path for the current platform.
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 · +3 tokens per session 7510f604ed7c
- 1mo ago First seen · 31 lines · 22 tokens per session scan A 3d6541646533
developer_pr_prep is a skill published in the GitHub repository siddsachar/row-bot (1,627 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 224 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
dev7-pr
Create a PR, push to GitHub, wait for Greptile review, address comments, and push final. Sub-skill of the /dev workflow.
dev6-review-fix
Apply fixes for review comments from dev5-review and commit. Sub-skill of the /dev workflow.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.