Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/YPares/rigup.nixnpx agentmods add skills/ypares/rigup.nix/agent-rig-systemWrote 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/ypares/rigup.nix/agent-rig-system)<a href="https://agentmods.dev/skills/ypares/rigup.nix/agent-rig-system"><img src="https://agentmods.dev/badge/skills/ypares/rigup.nix/agent-rig-system.svg" alt="Measured on agentmods" 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.00000 | $0.04122 |
| Opus 5 | $0.00000 | $0.02061 |
| Sonnet 5 | $0.00000 | $0.00824 |
| Haiku 4.5 | $0.00000 | $0.00412 |
Grade A, and why
agent-rig-system 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 8d 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Rig System
Overview
A rig is a collection of riglets that provide knowledge and tools for AI agents. Rigs and riglets are packaged as Nix flake outputs, so they can both be used inside the project defining them and by other projects depending on it.
Core Concepts
Riglet
A riglet is executable knowledge packaged with its dependencies, as a Nix module:
- Metadata: When should this riglet be used, is it production-ready or experimental, etc.
- Knowledge: SKILL.md + detailed
references/*.mdfiles documenting processes and recipes - Tools: Nix packages needed to execute those recipes
- Configuration: Settings to adapt tools' behaviour to project context
Rig
A project-level structure that declares which riglets are active:
- Uses
buildRigto compose riglet modules - Builds combined tool environment declaratively
- Exposes riglets' tools and documentation
rigup
A Nix library and CLI tool: http://github.com/YPares/rigup.nix
rigup Nix library
Main functions:
buildRig: evaluates riglet modules and ensures they comply with the riglet schema used by rigup. Returns the rig as an attrset:{ toolRoot = <derivation>; meta = { <riglet> = {...}; }; docAttrs = { <riglet> = <derivation>; }; docRoot = <derivation>; home = <derivation>; shell = <derivation>; }resolveProject: inspects theriglets/folder of a project and itsrigup.tomlto find out which riglets and rigs it defines. It callsbuildRigfor each rig in therigup.tomlgenManifest: generates a markdown+XML manifest file describing the contents of a rig, primarily for AI agent's consumptionmkRiglib: creates a set of utility functions to be used to define riglet Nix modules
Defined in {{repoRoot}}/lib/default.nix.
rigup CLI tool
A Rust app. It provides convenient access to rig outputs, via commands like rigup build and rigup shell, and project scaffolding via rigup new. This tool is meant for the user primarily. Agents should not have to call it directly.
What ships with it
5 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.
- 8d ago First seen · 414 lines · 0 tokens per session scan A 5c553436aeff
agent-rig-system is a skill published in the GitHub repository YPares/rigup.nix (88 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,122 tokens. 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
Summarize document text and identify its main claims, evidence, and unanswered questions.
jj-todo-workflow
Structured TODO commit workflow using JJ (Jujutsu). Use to plan tasks as empty commits with [task:] flags, track progress through status transitions, manage parallel task DAGs with dependency checking. Enforces completion discipline. Enables to divide work between Planners and Workers. Requires the working-with-jj…
package-npm-nix
Package npm/TypeScript/Bun CLI tools for Nix. Use when creating Nix derivations for JavaScript/TypeScript tools from npm registry or GitHub sources, handling pre-built packages or source builds with dependency management.
nushell-usage
Essential patterns, idioms, and gotchas for writing Nushell code. Use when writing Nushell scripts, functions, or working with Nushell's type system, pipelines, and data structures. Complements plugin development knowledge with practical usage patterns.
typst-writer
Write correct and idiomatic Typst code for document typesetting. Use when creating or editing Typst (.typ) files, working with Typst markup, or answering questions about Typst syntax and features. Focuses on avoiding common syntax confusion (arrays vs content blocks, proper function definitions, state management).
nushell-plugin-builder
Guide for creating Nushell plugins in Rust using nuplugin and nuprotocol crates. Use when users want to build custom Nushell commands, extend Nushell with new functionality, create data transformations, or integrate external tools/APIs into Nushell. Covers project setup, command implementation, streaming data, custom…