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 skills add runxhq/runx --skill governed-outboundgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/governed-outbound)<a href="https://agentmods.dev/skills/runxhq/runx/governed-outbound"><img src="https://agentmods.dev/badge/skills/runxhq/runx/governed-outbound/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.
<a href="https://agentmods.dev/skills/runxhq/runx/governed-outbound"><img src="https://agentmods.dev/badge/skills/runxhq/runx/governed-outbound.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00514 |
| Opus 5 | $0.00021 | $0.00257 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
governed-outbound 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governed Outbound
Deliver exact scrubbed outbound content in this order:
web-fetchperforms the bounded provider read and returns source readback.redact-piidetects semantic identifiers, deterministically scrubs the content, and withholds residual content unless its final verdict isready.- The exact scrubbed content and digest pass directly to
send-as; the caller selects only the provider and bounded target, never provider request grammar. send-as#sendplans principal and audience, derives the provider request and idempotency key, requests exact approval for the consequential send, performs it once, and requires independent provider readback.
The provider adapter remains separately configured and tenant-agnostic. Missing
adapter authority blocks before delivery; a plan or accepted request is never
reported as sent. Select the explicit plan runner when a provider-neutral
handoff is the requested outcome.
Composes
redact-pii#redact-piisend-as#plansend-as#sendweb-fetch#web-fetch
Stop conditions
- Missing or disallowed fetch inputs stop in
web-fetch. needs_revieworblockedredaction skips planning and delivery.- The plan runner never asks for performative approval; approval belongs to the
exact live send in
send-as#send. - A send plan whose principal, audience, or digest differs from the approved redaction fails deterministic finalization.
- Provider execution and readback must occur in the selected downstream adapter before any caller reports delivery.
Output
outbound_plan records completion: plan_only, provider_delivery: not_executed, source and redaction digests, the bounded send plan, and the selected provider actions. The scrubbed content remains available only in the redaction step output for the authorized downstream adapter.
Default delivery inputs are url, allowlist, channel, principal, and a
tenant-owned connector containing only provider and exact target.
operator_context is optional. The explicit plan runner omits connector.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 48 lines · 42 tokens per session scan A 606add55a1b1
governed-outbound is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 514 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-09-03.
Other skills, from other repositories
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.