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.
git clone --depth 1 https://github.com/rileyhilliard/agentrcWrote 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/commands/rileyhilliard/agentrc/test)<a href="https://agentmods.dev/commands/rileyhilliard/agentrc/test"><img src="https://agentmods.dev/badge/commands/rileyhilliard/agentrc/test/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/commands/rileyhilliard/agentrc/test"><img src="https://agentmods.dev/badge/commands/rileyhilliard/agentrc/test.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.00005 | $0.00275 |
| Opus 5.5 | $0.00002 | $0.00110 |
| Sonnet 5.5 | $0.00001 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade B, and why
test scanned grade B with 1 finding 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 1mo 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
**DELEGATION ONLY**: Do NOT run any commands or investigate the codebase yourself. Your only job is to immediately invoke the `ce:haiku` agent via Task tool, passing the prompt template below with `$ARGUMENTS` substitute What it actually says
DELEGATION ONLY: Do NOT run any commands or investigate the codebase yourself. Your only job is to immediately invoke the ce:haiku agent via Task tool, passing the prompt template below with $ARGUMENTS substituted.
Task Prompt for Haiku Agent
Run tests and analyze any failures.
User arguments: $ARGUMENTS
(If provided, use as the test command. Otherwise, auto-detect.)
**Step 1: Detect the test command** (if no custom command provided)
- Check for package.json (yarn test or npm test)
- Check for pytest.ini or setup.py (pytest)
- Check for Cargo.toml (cargo test)
- Check for Makefile with test target
- Check for go.mod (go test ./...)
**Step 2: Run the tests**
Execute the detected or provided test command.
**Step 3: Analyze failures** (if any occur)
- Parse the failure messages
- Identify root causes
- Reference specific file:line locations
- Suggest fixes
**Step 4: Report results**
Provide a summary including:
- Total tests run
- Passed/failed/skipped counts
- For failures: clear, actionable feedback
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.
- 1mo ago First seen · 39 lines · 5 tokens per session scan B ebe1e385dc1c
test is a command published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 8mo ago), licensed MIT. It adds 5 tokens to every session and 275 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.