send-as skillA
send-as is agent-read markdown (skill) from runxhq/runx: Send one digest-bound provider-neutral message or campaign action through a compatible connector, with an explicit plan runner and approval plus readback at the live-delivery boundary..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Send As Govern a message, campaign, or notification sent on behalf of a principal. The default `send` runner performs one delivery through a compatible normalized connector and closes only after independent provider readback. `plan` is the explicit no-effect runner. `apply` consumes an existing `runx.send_as.plan.v1` packet without planning again, and `verify` consumes the provider mutation result without sending again. Provider-specific skills can compose these phase runners while retaining the same authority model. ## What this skill does `send-as` binds the principal, provider, channel, recipients or audience, content digest, consent basis, preflight checks, and approval gate. The caller selects only a compatible provider and bounded target; it does not author provider operations, result fields, payload plumbing, or retry keys. Runx derives a canonical `message.send` request from the approved plan, binds its idempotency key to a native digest, applies it under one approval, and verifies the stable identity with `message.read`. It refuses to treat a draft, preview, mutation acknowledgement, or test message as live delivery. A live send is …
Read the whole file at its exact version.
How to install
mdr add runxhq/runx/send-as@git:20260811.bade9bfmdr add runxhq/runx/send-as@sha256:c9e832105fd33f03Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3ez6ru36uvsd4to7)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260811.bade9bf latest | 2026-08-11 | bade9bf | 8,085 B | A | view · diff |
| git:20260810.e284078 | 2026-08-10 | e284078 | 7,930 B | A | view · diff |
| git:20260808.8b7af2a | 2026-08-08 | 8b7af2a | 7,409 B | A | view · diff |
| git:20260713.2f8c42f | 2026-07-13 | 2f8c42f | 6,252 B | A | view · diff |
| git:20260621.f707966 | 2026-06-21 | f707966 | 5,913 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8085 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
runxhq/runx · 93 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3ez6ru36uvsd4to7 GET https://markdownregistry.com/api/v1/resolve?ref=runxhq/runx/send-as GET https://markdownregistry.com/api/v1/blob/c9e832105fd33f032c69674790d9b03bb0191d30e866d132038273730ea94ead
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.