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 mvschwarz/openrig --skill rig-bundles-and-shareable-artifactsgit 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/rig-bundles-and-shareable-artifacts)<a href="https://agentmods.dev/skills/mvschwarz/openrig/rig-bundles-and-shareable-artifacts"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/rig-bundles-and-shareable-artifacts/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/mvschwarz/openrig/rig-bundles-and-shareable-artifacts"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/rig-bundles-and-shareable-artifacts.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.00078 | $0.00950 |
| Opus 5 | $0.00039 | $0.00475 |
| Sonnet 5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
rig-bundles-and-shareable-artifacts 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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rig Bundles and Shareable Artifacts
A rig bundle is a packaged, shareable artifact that can instantiate an opinionated OpenRig topology and workflow. It may include:
- rig specs
- agent specs
- workflow specs
- startup files
- skills or skill references
- operating-mode declarations
- proof expectations
- supporting fragments
Shareable artifact is broader than bundle: specs, bundles, skills, workflows, and extensions can all be shared. A bundle is the packaged form for "load this topology and way of working."
Use this when
- Authoring a bundle from a proven lab pattern
- Installing a bundle (
rig bundle install <path>) - Inspecting a bundle before install (
rig bundle inspect <path>) - Reasoning about bundle vs extension boundary (bundle declares topology + workflow; extension adds behavior)
- Auditing a bundle for portability — does it work on a clean OpenRig environment, or only the author's machine?
Don't use this when
- The work is a one-off topology you won't reuse. Specs alone are sufficient.
- The intent is to add runtime behavior (commands, views, dashboards). Use
extension-and-user-workspace, not bundles. - You want to ship a workflow as a daemon feature. Bundle is the path before daemon promotion.
The bundle vs extension boundary (load-bearing)
| Concept | Declares | Example |
|---|---|---|
| Bundle | Rig shape + workflow ("load this topology and way of working") | A Velocity Team bundle |
| Extension | Behavior added to user workspace/runtime | A custom command, view, or dashboard |
Don't confuse them. A bundle is opinionated content; an extension is added behavior. Both can be shareable artifacts, but they're structurally distinct.
Failure modes (4)
- A bundle works only on the operator's machine because paths, providers, or credentials are implicit. Bundles must be self-describing for a clean OpenRig environment.
- A bundle includes too much local state and becomes a backup archive instead of a reusable artifact. Bundle is the intended shape, not the current state of one specific install.
- A bundle declares topology but omits proof expectations or workflow mode. Topology alone doesn't tell users what "working as advertised" means.
- Users cannot inspect what a bundle will create before installing it.
rig bundle inspectmust show what will be created without side effects.
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.
- 10d ago First seen · 102 lines · 78 tokens per session scan A e9d5103f419b
rig-bundles-and-shareable-artifacts is a skill published in the GitHub repository mvschwarz/openrig (66 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 950 once invoked, about $0.0004 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
dynamic-resources
Example skill loaded from resourcesdiscover.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
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.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.
run-test-suite-after-registration-changes
When delegating a task affected by this skill, include.