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 claude_code_delegationgit 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/claude_code_delegation)<a href="https://agentmods.dev/skills/siddsachar/row-bot/claude_code_delegation"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/claude_code_delegation/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/claude_code_delegation"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/claude_code_delegation.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.00031 | $0.02247 |
| Opus 5.5 | $0.00012 | $0.00899 |
| Sonnet 5.5 | $0.00006 | $0.00449 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
claude_code_delegation 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 1mo 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When the user asks to use Claude Code, coordinate Claude Code, delegate coding work, have another coding agent implement/review/refactor something, or compares Row-Bot with Hermes-style Claude Code orchestration, use this workflow.
You are the coordinator. Claude Code is the delegated coding worker. Keep ownership of the user's goal, safety boundaries, summary, follow-up checks, and final explanation.
Core Principles
- Prefer print mode first — Use
claude -pfor most tasks. It runs one bounded task, returns output, and exits. This works well with Row-Bot'srun_commandtool and avoids interactive terminal state. - Keep Row-Bot in charge — Do not hand off the whole conversation. Give Claude Code a clear task, collect its result, inspect what changed, run appropriate checks, and report back to the user.
- Use the Shell tool deliberately — Use
run_commandfor Claude Code CLI calls. Row-Bot's shell tool persists the working directory per conversation and approval-gates non-safe commands. - Set the project directory explicitly — Before delegating, confirm or set the repo directory with
pwd/Get-Locationandcd/Set-Location. Claude Code resume and context behaviour depend on the current directory. - Constrain autonomy — Always use limits such as
--allowedTools,--max-turns, and, when available,--max-budget-usdfor print-mode tasks. - Avoid permission bypass — Do not use
--dangerously-skip-permissionsunless the user explicitly asks and understands that Claude Code may edit files and run commands without per-action prompts. - Do not forward secrets — Never include API keys, tokens, Row-Bot memory, private notes, or sensitive user data in a Claude Code prompt unless the user explicitly asks for that specific context to be shared.
Prerequisite Checks
Before the first delegation in a project or session, check whether Claude Code is available and authenticated:
claude --version
claude auth status
claude doctor
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.
- 1mo ago First seen · 186 lines · 31 tokens per session scan A d621575ae814
claude_code_delegation is a skill published in the GitHub repository siddsachar/row-bot (1,627 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 2,247 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
code-review
Performs structured code review on a file or directory.
pr-review
Review a GitHub pull request and post one formal review — advance the existing discussion and give precision-first, high-signal feedback. Judgement on the diff, not a build gate — CI validates that it builds, and a targeted probe is allowed as evidence. Use when asked to review a PR or on a cron PR scan.
code-review
The shared rubric for reviewing a code change — precision-first, high-signal findings only (Critical/Important), what to check (correctness, contracts between producer and consumer, security, edge cases, regression risk, test coverage), and what is NOT a finding (pre-existing issues, linter territory, aspirational…
codex-review
A Herdr skill that starts an independent Codex reviewer to examine changes, commits, files, or plans in read-only mode. Codex is an AI coding assistant, and Herdr is used here to coordinate that separate review session.
code-review
A code-review checklist for examining code without rewriting it. It checks correctness, security, readability and performance, then labels findings by seriousness.
Code Review
Review a diff or PR for concrete behavioral defects and Home23 invariants.