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 skills/stevegeek/claude-ruby-plugins/rbs-filesnpx skills add stevegeek/claude-ruby-plugins --skill rbs-filesgit clone --depth 1 https://github.com/stevegeek/claude-ruby-pluginsWrote 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/stevegeek/claude-ruby-plugins/rbs-files)<a href="https://agentmods.dev/skills/stevegeek/claude-ruby-plugins/rbs-files"><img src="https://agentmods.dev/badge/skills/stevegeek/claude-ruby-plugins/rbs-files.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 | $0.00035 | $0.01406 |
| Opus 5 | $0.00017 | $0.00703 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
rbs-files 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 4d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standalone RBS Files
Write type signatures in separate .rbs files in a sig/ directory. Ruby source files remain unchanged.
Quick Start
# sig/person.rbs
class Person
attr_reader name: String
attr_reader age: Integer?
def initialize: (String name, ?Integer? age) -> void
def greet: () -> String
end
File Structure
project/
├── lib/
│ └── person.rb # Ruby implementation
├── sig/
│ ├── person.rbs # Type signatures
│ ├── _private/ # Hidden from library users
│ │ └── internal.rbs
│ └── manifest.yaml # Stdlib dependencies
└── Steepfile
Class and Module Declarations
# Basic class
class User
end
# With superclass
class Admin < User
end
# With type parameters
class Container[T]
end
# Module
module Logging
end
# Module with self-type constraint
module Enumerable[Elem] : _Each[Elem]
end
Method Definitions
class Calculator
# Instance method
def add: (Integer, Integer) -> Integer
# Singleton (class) method
def self.create: () -> Calculator
# Module function (both singleton and private instance)
def self?.sqrt: (Numeric) -> Float
# Visibility
private def internal: () -> void
end
Method Type Syntax
# Required positional
def foo: (String, Integer) -> void
# Optional positional (? prefix)
def foo: (String, ?Integer) -> void
# Rest positional
def foo: (*String) -> void
# Required keyword
def foo: (name: String) -> void
# Optional keyword
def foo: (?name: String) -> void
# Keyword rest
def foo: (**String) -> void
# Block (required)
def foo: () { (String) -> Integer } -> void
# Block (optional, ? before brace)
def foo: () ?{ (String) -> Integer } -> void
# Complex signature
def foo: (
String, # Required positional
?Integer, # Optional positional
*Symbol, # Rest positional
name: String, # Required keyword
?age: Integer, # Optional keyword
**untyped # Keyword rest
) { (String) -> void } -> Array[String]
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.
- 4d ago First seen · 296 lines · 35 tokens per session scan A ca46b521ead3
rbs-files is a skill published in the GitHub repository stevegeek/claude-ruby-plugins (19 stars, last pushed 4mo ago), licensed Unlicense. It adds 35 tokens to every session and 1,406 once invoked, about $0.0002 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 skills, from other repositories
rails-expert
Rails 7+ specialist that optimizes Active Record queries with includes/eagerload, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building…
contributing
Contribute to RubyLLM - set up the repo, run and record specs, add providers or chat options, work on the Rails integration, and edit docs. Use when fixing a bug, building a feature, writing specs, or changing documentation in the RubyLLM codebase.
rails-conventions
Rootstrap Rails conventions. Use when writing, reviewing, or editing any Rails code — controllers, models, migrations, routes, views, mailers, initializers, locale files, or Rails config. Covers routing, ActiveRecord, migrations, i18n, time zones, mailers, assets, Bundler groups, and logging.
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
rails-upgrade
Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 2.3 through 8.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes. Based on FastRuby.io methodology and "The…
ruby-conventions
Rootstrap Ruby style conventions. Use when writing, reviewing, or editing any Ruby source file (.rb, .rake, Gemfile, Rakefile, .gemspec, config.ru) to ensure code follows the Rootstrap Ruby style guide — covers layout, syntax, naming, classes/modules, exceptions, collections, strings, regexes, metaprogramming, and…