A messaging tool for talking to the project’s orchestrator or to another coding session in the same repository. It supports asking questions, sending notices, reading replies, and seeing who is working.

Use it to ask the orchestrator for information, notify a peer, read earlier messages, or list active workers.

It avoids switching between sessions or guessing how to contact another worker. It sends peer messages through the repository’s shared coordination system.

orc — Skill for Claude Code by restarter/lets-workflow

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add restarter/lets-workflow

Claude Code

/plugin install lets

Made for: Claude Code.

Or install lets, the plugin that ships this one along with the rest of its 20 skills, 26 commands, 16 agents.

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/skills/restarter/lets-workflow/orc/github.svg)](https://agentmods.dev/skills/restarter/lets-workflow/orc)

Your own site

<a href="https://agentmods.dev/skills/restarter/lets-workflow/orc"><img src="https://agentmods.dev/badge/skills/restarter/lets-workflow/orc/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/skills/restarter/lets-workflow/orc"><img src="https://agentmods.dev/badge/skills/restarter/lets-workflow/orc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 171 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,367 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.00171	$0.05367
Opus 5.5	$0.00068	$0.02147
Sonnet 5.5	$0.00034	$0.01073
Haiku 4.5	$0.00017	$0.00537

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

Security

Grade A, and why

orc 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 2d 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.

plugins/lets/skills/orc/SKILL.md · 189 lines

How it starts

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

Orc - peer messages

Talk to the repo's orchestrator or a named peer session: ask / ping / read / tell / who, and from an orchestrator standing on|off. The ONLY place in LETS that sends a peer message, always through the harness's SendMessage. Go (lets peers) resolves, lists and reads; the harness delivers; this skill composes and decides nothing on a peer's behalf.

IMPORTANT: If the spec below invokes any deferred tool (e.g. AskUserQuestion, SendMessage, ListAgents), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.

Args

verb=ask|ping|read|tell|who|standing target="<name>" text=<rest> [footer=none] [--yes] [via=hub] - target is optional for ask / ping (default: this chat's orchestrator) and REQUIRED for tell, quoted. --yes (the user typed it) skips the Send? question in Step 4, not the message itself - see the Preview gate. via=hub is passed only by /lets:hub, never typed or inferred. An older caller's session / repo-index args are ignored: a peer is addressed by name. From natural language: map the request to a verb (a question for an answer -> ask; an FYI -> ping or tell; "what did X say" -> read; "who is working" -> who; "let my bound sessions and me talk without asking" (either direction) / "stop that" -> standing on / standing off). Any other verb: say so and stop.

verb	sends	waits	target required
`ask`	yes	the peer's reply, relayed when it lands	no (orchestrator)
`ping`	yes	no	no (orchestrator)
`tell`	yes	no	yes
`read [N]`	no	no	no
`who`	no	no	no
`standing on\|off`	no (writes the grant)	no	no

Step 1: Resolve the target

Read ${CLAUDE_PLUGIN_ROOT}/protocol/peers.md before this step unless its text is in your current context (boundary carve-outs: peers, hub; standing authorization).

Read the full file on GitHub · 189 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.

2d ago Changed · +10 lines · +14 tokens per session 7a5d96de89af
3d ago Changed · +39 lines · +33 tokens per session 5733d4b0d6a7
19d ago Changed · +4 lines 948f3ac9080d
20d ago Changed 14f2c0baee8c
22d ago Changed · +2 lines 69e172e8e127
23d ago Changed · +2 lines 29ed9977e452
26d ago Changed · +9 lines 07045ce9c872
27d ago Changed 2b3eb65fc9d0
28d ago Changed · +1 lines 324ee3d137fe
1mo ago First seen · 122 lines · 124 tokens per session scan A eddb16fa3170

Subscribe to this mod's changes

orc is a skill published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 171 tokens to every session and 5,367 once invoked, about $0.0007 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-09-16.

Building agents Claude Code Code review ai-agents claude-code-plugin cli developer-tools

dekko-verify

Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…

aahlijia/dekko · 151 tokens

dekko-review-context

Give a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (/code-review, /review, or an equivalent) against a diff in a repo with a .dekko/ directory.

aahlijia/dekko · 74 tokens

triage-report

Drain the .review/ report queue. Resolves un-triaged scan/audit reports (producer-agnostic — check-docs-consistency and any other scanner), dispatches the triage-report subagent (Sonnet) one report at a time for per-finding dispositions (promote / patch / dup / needs-investigation / dismiss), then the gateway absorbs…

RockyHong/super-bootstrap · 151 tokens

orc