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 agentmods add commands/rileyhilliard/rr/setupgit clone --depth 1 https://github.com/rileyhilliard/rrWhat 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 | $0.00031 | $0.01745 |
| Opus 5 | $0.00015 | $0.00873 |
| Sonnet 5 | $0.00006 | $0.00349 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade F, and why
rr:setup scanned grade F with 4 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
ssh <host-alias> "curl -LO https://go.dev/dl/go1.22.0.linux-amd64.tar.gz && sudo tar -C /usr/local -xzf go1.22.0.linux-amd64.tar.gz" Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- **"handshake failed" but ssh works**: Key not in agent. Run `ssh-add ~/.ssh/id_rsa` Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
ssh <host-alias> "curl -LsSf https://astral.sh/uv/install.sh | sh" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
ssh <host-alias> "curl -LsSf https://astral.sh/uv/install.sh | sh" How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rr Setup
Use the rr skill
Set up and verify rr for this project. Work through each step in order, fixing issues as they arise.
Step 1: Global Config
Check if ~/.rr/config.yaml exists with valid hosts:
cat ~/.rr/config.yaml
If missing or empty, ask the user for their remote machine details and help create the config. Refer to the rr skill for config format.
Step 2: Project Config
Detect the project's tech stack by checking for package.json, go.mod, pyproject.toml, Makefile, Cargo.toml, etc.
Create or update .rr.yaml with:
- Sync exclusions appropriate for the detected stack
- Useful tasks based on the tooling (test, build, lint, etc.)
Refer to the rr skill for config format and task syntax.
Step 3: Verify SSH
Run diagnostics:
rr doctor
If SSH fails, debug systematically:
- Test manual SSH:
ssh <host-alias> - Check SSH config:
grep -A5 "<host-alias>" ~/.ssh/config - Common fixes:
- Password prompt: needs key-based auth
- Host not found: add to
~/.ssh/config - Timeout: host unreachable, try alternative address
- "handshake failed" but ssh works: Key not in agent. Run
ssh-add ~/.ssh/id_rsa
Important for passphrase-protected keys: Ensure your SSH config includes AddKeysToAgent yes and UseKeychain yes (macOS) so keys are automatically loaded:
Host your-host
HostName 192.168.x.x
User youruser
IdentityFile ~/.ssh/id_rsa
AddKeysToAgent yes
UseKeychain yes
This prevents "handshake failed" errors where ssh works but rr cannot connect.
Step 4: Test Execution
Verify basic execution works:
rr exec "pwd"
Then test with sync:
rr run "ls -la"
If the remote directory is wrong, check the dir setting in global config.
Step 5: Configure and Verify Requirements
rr supports declarative requirements via the require: field. Add required tools to .rr.yaml:
# .rr.yaml
require:
- go # Go projects
- node # Node projects
- python3 # Python projects
- uv # Python package manager
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.
- today First seen · 258 lines · 31 tokens per session scan F 6256af99f3f2
rr:setup is a command published in the GitHub repository rileyhilliard/rr (195 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 1,745 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it F with 4 findings (asks for root, reaches for credential files, downloads and executes remote code). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.