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 agentmods add skills/mvschwarz/openrig/messaging-the-humannpx skills add mvschwarz/openrig --skill messaging-the-humangit clone --depth 1 https://github.com/mvschwarz/openrigWrote 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/mvschwarz/openrig/messaging-the-human)<a href="https://agentmods.dev/skills/mvschwarz/openrig/messaging-the-human"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/messaging-the-human.svg" alt="Measured on agentmods" height="20"></a>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.00042 | $0.00799 |
| Opus 5 | $0.00021 | $0.00400 |
| Sonnet 5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
messaging-the-human 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 6d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Messaging the Human
The human is an addressable participant, but their attention is scarce and they may not be at a terminal. Anything that must survive their absence needs a durable queue row; the gateway turns the human blocker on that row into the external notification.
Any seat may contact the human directly for a real escalation. Orchestrators and product managers may also send updates they judge the human would want to know. Do not add a routing intermediary merely because of your role.
The supported route
First discover the registered human identity. Never invent or remember an address:
rig gateway human list --json
Use humans[].entityId to derive the durable blocker as <entityId>@host.
The entity id must use the human-seat prefix (human or human-...); if it
does not, stop and repair the registration rather than guessing. The returned
humans[].address is the gateway delivery address, not the --on value. If no
unambiguous registered human is returned, stop: registration is lifecycle work
(rig gateway human add --help), not an address to guess.
Keep the work row owned by the agent who must resume it, then park that row on the registered human:
rig queue block <qitem-id> --on <entityId>@host \
--summary "<decision owed>" \
--evidence-ref "<durable artifact the human should judge>" \
--continuation "<what resumes after the answer>"
The gateway resolves the registered human to the configured connector, sends the Slack notification, and records its receipt on the same row. Confirm the effect from the append-only history:
rig queue transitions <qitem-id>
The row is the obligation and the audit trail. Slack is the attention leg. A reply resolves the durable blocker and wakes the row owner; it does not create a second private work stream.
When to use it
Escalate directly when only the human can supply the missing capability:
- a decision or irreversible judgment only they own;
- access, credentials, authority, or capacity only they can grant;
- an external action only they can perform;
- a security-class or provider/model-fallback event they need to know about.
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.
- 6d ago First seen · 99 lines · 42 tokens per session scan A 2ef9b44aa6f4
messaging-the-human is a skill published in the GitHub repository mvschwarz/openrig (65 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 799 once invoked, about $0.0002 per session on Opus 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
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
ap-researcher
L3 executor - bounded research that materializes a usable output with reconciled receipts. Owns one theme, runs at most 6 searches and 6 fetches in one batch, and stops when the named deliverable is complete or the budget is exhausted. Does not spawn.
ap-scoper
L3 useful-first roadmap author or complementary scout - proves capability when needed, inspects the real repository, and contributes to one executable ROADMAP.md without spawning.
ap-execharness-resolver
L3 executor - EXECHARNESS RESOLVE. Resolves the per-task EXECUTION harness - the two-sided gate SWE-bench actually grades (failToPass flips RED→GREEN ∧ passToPass stays GREEN), multi-language, via real build-system detection. Ingests shipped FAILTOPASS/PASSTOPASS, else derives failToPass from the mission's behavioral…