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/butterbase-ai/butterbase-skillsWrote 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/butterbase-ai/butterbase-skills/debug-rls)<a href="https://agentmods.dev/commands/butterbase-ai/butterbase-skills/debug-rls"><img src="https://agentmods.dev/badge/commands/butterbase-ai/butterbase-skills/debug-rls.svg" alt="Measured on agentmods" 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.00017 | $0.00042 |
| Opus 5 | $0.00009 | $0.00021 |
| Sonnet 5 | $0.00003 | $0.00008 |
| Haiku 4.5 | $0.00002 | $0.00004 |
Grade A, and why
debug-rls 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 9d 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 butterbase-skills:debug-rls skill to systematically diagnose and fix the issue.
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.
- 9d ago First seen · 6 lines · 17 tokens per session scan A 18bd98ac7c5f
debug-rls is a command published in the GitHub repository butterbase-ai/butterbase-skills (533 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 42 once invoked, about $0.0001 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 commands, from other repositories
audit-performance
Performance audit. Detects N+1 queries, memory issues, caching gaps, inefficient loops, batch processing problems, algorithm complexity, connection pools, serialization overhead.
codesage-reset
Drop a project's CodeSage index and rebuild from scratch (use after settings changes, device switches, or corruption).
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
sqlscript-validate
Validates SQLScript code for syntax, patterns, and best practices with auto-fix capability.
pg-health
Read-only PostgreSQL health check with pgbot, then a prioritized diagnosis.
data-flow-analysis
Trace how data flows through the system from input to output.