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 hyperlogue/r3 --skill publish-artifacts-to-r3git clone --depth 1 https://github.com/hyperlogue/r3Wrote 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/hyperlogue/r3/publish-artifacts-to-r3)<a href="https://agentmods.dev/skills/hyperlogue/r3/publish-artifacts-to-r3"><img src="https://agentmods.dev/badge/skills/hyperlogue/r3/publish-artifacts-to-r3/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/hyperlogue/r3/publish-artifacts-to-r3"><img src="https://agentmods.dev/badge/skills/hyperlogue/r3/publish-artifacts-to-r3.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.00286 |
| Opus 5.5 | $0.00022 | $0.00114 |
| Sonnet 5.5 | $0.00011 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00029 |
Grade A, and why
publish-artifacts-to-r3 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.
What it actually says
Run r3 guide once per session to get instructions for publishing artifacts and
responding to feedback. This tries the executable on PATH; if it succeeds,
use that executable for subsequent commands.
If r3 is unavailable, run the latest published release with npm:
npx --yes @hyperlogue/r3@latest guide
With Bun:
bunx --bun @hyperlogue/r3@latest guide
On NixOS, use the Nix flake:
nix run github:hyperlogue/r3#r3 -- guide
Follow the executable's guide for publication and the feedback workflow. Before
preparing an artifact kind for the first time in a session, read its preparation
guide using the guide html, guide files, or guide diff subcommand.
Use --help for command details.
Share the returned artifact URL. When responding to feedback, publish changes as a new version under the same artifact ID and reply to its threads. This keeps the comments and version history together.
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 First seen · 36 lines · 54 tokens per session scan A 2f0607b64330
publish-artifacts-to-r3 is a skill published in the GitHub repository hyperlogue/r3 (45 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 286 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…