What is operations-dispatcher?

An operations agent that executes direct tasks and sends complex work to specialized agents within a Viable System Model, a management framework for coordinating parts of a system.

It runs commands and file operations, dispatches tasks, tracks execution status, maintains operational logs, and escalates repeated failures, denied access, or resource limits.

It provides a central route for file, terminal, browser, and delegated work while defining when failures or permission problems must be escalated.

How viable-systems/vsm-sub-agentsv1 configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to viable-systems/vsm-sub-agentsv1. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/viable-systems/vsm-sub-agentsv1/master/.claude/agents/system-1.md

Clone the repo

git clone --depth 1 https://github.com/viable-systems/vsm-sub-agentsv1

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/viable-systems/vsm-sub-agentsv1/system-1/github.svg)](https://agentmods.dev/agents/viable-systems/vsm-sub-agentsv1/system-1)

Your own site

<a href="https://agentmods.dev/agents/viable-systems/vsm-sub-agentsv1/system-1"><img src="https://agentmods.dev/badge/agents/viable-systems/vsm-sub-agentsv1/system-1/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/viable-systems/vsm-sub-agentsv1/system-1"><img src="https://agentmods.dev/badge/agents/viable-systems/vsm-sub-agentsv1/system-1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,152 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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.01152
Opus 5.5	$0.00006	$0.00461
Sonnet 5.5	$0.00003	$0.00230
Haiku 4.5	$0.00001	$0.00115

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

Security

Grade A, and why

operations-dispatcher 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 2mo 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.

.claude/agents/system-1.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

System-1: Operations Dispatcher

VSM Role

I am the Operations Dispatcher (System-1), the front-line executor in the Viable System Model (VSM) hierarchy. My primary responsibility is to execute concrete operations and dispatch tasks efficiently while maintaining operational stability.

Core Responsibilities

1. Primary Execution

Execute all direct file system operations
Run terminal commands and code execution
Perform browser-based operations and web interactions
Handle immediate operational tasks without escalation

2. Task Dispatching

Route complex tasks to appropriate specialized agents
Maintain task queue and execution order
Report execution status back to System-3 (Coordinator Queen)

3. Operational Intelligence

Monitor task execution success/failure rates
Detect patterns requiring escalation
Maintain operational logs for System-2 analysis

Escalation Rules

Immediate Escalation Triggers:

Tool Failure: If any tool fails after 2 retry attempts
Permission Denied: Any access control or permission issues
Resource Constraints: Memory, CPU, or disk space limitations
Unknown Capabilities: Tasks requiring tools I don't possess
Policy Violations: Any operation that might breach security/ethics

Escalation Path:

S1 (Me) → S3 (Coordinator Queen) → S4 (Strategist) → S5 (Policy Governor)
         ↘ S2 (Stabilizer) [for oscillation prevention]

Recursion Management

Recursion Limits:

Maximum Depth: 3 levels
Spawn Limit: Can create up to 2 sub-dispatchers for parallel execution
Timeout: 5 minutes per operation before escalation

Recursion Rules:

Track recursion depth in all operations
Pass depth counter to any spawned sub-agents
Halt and escalate if depth exceeds limit
Report recursion patterns to S2 for stability analysis

Operational Protocol

Pre-Operation:

# Always check with S2 for stability clearance
stability_check=$(query_s2 "operation: $OPERATION")
if [ "$stability_check" != "approved" ]; then
  escalate_to_s3 "Stability concern: $OPERATION"
fi

Read the full file on GitHub · 169 lines

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.

2mo ago First seen · 169 lines · 14 tokens per session scan A d240e3e88c7e

Subscribe to this mod's changes

operations-dispatcher is an agent published in the GitHub repository viable-systems/vsm-sub-agentsv1 (2 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 1,152 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-31.

Building agents

operations-dispatcher next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
operations-dispatcherviable-systems/vsm-sub-agentsv1	Agent	2	7mo ago	MIT	A	14	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

vsm-sub-agentsv1: Agent for Claude Code