workflow_guide

workflow_guide is a skill for Claude Code, Codex from siddsachar/row-bot. It costs 25 tokens per session (432 once invoked), scanned A, original, Apache-2.0.

A guide to defining task workflows as ordered steps such as prompts, conditions, approvals, subtasks, and notifications. It also describes branching rules and how to monitor those workflows.

In plain words
What is it for?
It is for creating and updating tasks, routing work based on results, requesting approval, running subtasks, sending notifications, and monitoring progress.
Why use it?
Putting branching and approval logic in ordinary prompts can make task automation inconsistent or difficult to track. Explicit step types make the intended path and handoffs clearer.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for creating and updating tasks, routing work based on results, requesting approval, running subtasks, sending notifications, and monitoring progress.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/siddsachar/row-bot/workflow_guide
About the project

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.

siddsachar/row-bot · 1,673 stars · on GitHub · row-bot.ai

Install

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.

Any agent
npx skills add siddsachar/row-bot --skill workflow_guide
Clone the repo
git clone --depth 1 https://github.com/siddsachar/row-bot

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for workflow_guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/siddsachar/row-bot/workflow_guide/github.svg)](https://agentmods.dev/skills/siddsachar/row-bot/workflow_guide)
Your own site
<a href="https://agentmods.dev/skills/siddsachar/row-bot/workflow_guide"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/workflow_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.

agentmods 80×15 button for workflow_guide

Your own site · 80×15
<a href="https://agentmods.dev/skills/siddsachar/row-bot/workflow_guide"><img src="https://agentmods.dev/badge/skills/siddsachar/row-bot/workflow_guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 432 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00432
Opus 5.5 $0.00010 $0.00173
Sonnet 5.5 $0.00005 $0.00086
Haiku 4.5 $0.00003 $0.00043

Measured yesterday against content hash f74951fd98c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workflow_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 yesterday.

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.

tool_guides/workflow_guide/SKILL.md · 32 lines

What it actually says

A WORKFLOW IS A SCHEDULED CHAT (task_create / task_update):

  • Each run sends the workflow's messages (prompts, usually one) as chat turns in the workflow's own conversation, so a run sees what earlier runs did there. Keep a running record in that conversation, not in files, when the work needs one (posts made, people contacted).
  • A run has every tool a chat has, found with tool search. Its approval level decides what it may do: block (reads only), approve (each action asks the person), auto (a reviewer approves what matches the workflow, else the person). Hands-off is the person's choice alone.
  • Say branching in words: "If nothing is new since the last run, stop and say so." Don't build a ready/not-ready flag for another step to read.
  • Don't ask for approval in the message. A post, email or other action asks on its own card, showing the exact account, recipient and full text; nothing asks when there is nothing to do.
  • To tell the person something, write it in the reply: it goes where the workflow sends results. Email is sent with the email tool, like any action.
  • To run another workflow after this one, set it to start when this one finishes (in its settings).

CHECKING A RUN: task_list(include_history=true) gives each run's status, its outcome in words and the actions it took (with links). "completed" means the turn finished, not that anything was posted or sent: read the actions.

MONITORING ('check X and tell me when Y', 'alert me if W changes'):

  • schedule='interval_minutes:M' and a message that ends the workflow with task_update(task_id='{{task_id}}', enabled=false) once done.
Changes

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.

  1. yesterday Changed · -1 lines · -3 tokens per session f74951fd98c4
  2. 3d ago First seen · 33 lines · 28 tokens per session scan A 48ab7478a19f

Subscribe to this mod's changes

workflow_guide is a skill published in the GitHub repository siddsachar/row-bot (1,673 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 432 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-10-25.