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/optimize)<a href="https://agentmods.dev/commands/rileyhilliard/agentrc/optimize"><img src="https://agentmods.dev/badge/commands/rileyhilliard/agentrc/optimize/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/optimize"><img src="https://agentmods.dev/badge/commands/rileyhilliard/agentrc/optimize.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.00007 | $0.00216 |
| Opus 5.5 | $0.00003 | $0.00086 |
| Sonnet 5.5 | $0.00001 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
optimize 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 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.
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
Use the Skill tool to invoke the optimizing-performance skill to analyze code for performance issues and suggest optimizations.
Arguments:
$ARGUMENTS: Optional file path or area to focus on (defaults to unstaged changes)
If $ARGUMENTS is empty:
- Run
git diffto get unstaged changes - Focus on optimizing the unstaged changes
If $ARGUMENTS is provided:
- Use it as the focus area for optimization
When invoking the ce:optimizing-performance skill:
"Analyze code for performance issues and suggest optimizations.
Focus area: [unstaged changes from git diff OR $ARGUMENTS]
Provide:
- Specific file:line references for each issue
- Explanation of the performance impact
- Code examples showing the optimization
- Estimated improvement (if measurable)
- Cost-benefit analysis for each proposed optimization
Prioritize high-impact optimizations over micro-optimizations."
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 · 37 lines · 7 tokens per session scan A 64e99f5829b1
optimize is a command published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 216 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
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…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.