Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dallay/agents-skillsnpx agentmods add skills/dallay/agents-skills/ruby-developmentWrote 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/dallay/agents-skills/ruby-development)<a href="https://agentmods.dev/skills/dallay/agents-skills/ruby-development"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/ruby-development/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/skills/dallay/agents-skills/ruby-development"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/ruby-development.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.00046 | $0.02533 |
| Opus 5.5 | $0.00018 | $0.01013 |
| Sonnet 5.5 | $0.00009 | $0.00507 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
ruby-development scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
urls.map { |url| fetch(url) }.each(&block) How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ruby Development
Production patterns and idioms for Ruby programming, covering project structure, gems, blocks, testing, metaprogramming, and error handling.
When to Use This Skill
- Starting or structuring a Ruby project
- Working with Bundler and gem dependencies
- Writing idiomatic Ruby with blocks, procs, and lambdas
- Testing with RSpec or Minitest
- Applying Ruby style conventions
- Writing Rake tasks for automation
- Understanding metaprogramming basics
Core Concepts
1. Project Layout
myapp/
├── lib/
│ ├── myapp.rb # Main entry, requires sub-modules
│ └── myapp/
│ ├── client.rb
│ ├── parser.rb
│ └── errors.rb
├── spec/ # RSpec tests
│ ├── spec_helper.rb
│ ├── myapp/
│ │ ├── client_spec.rb
│ │ └── parser_spec.rb
│ └── support/
│ └── shared_contexts.rb
├── bin/
│ └── myapp # CLI executable
├── Gemfile
├── Gemfile.lock
├── Rakefile
├── myapp.gemspec # If building a gem
└── README.md
2. Key Principles
| Principle | Ruby Idiom |
|---|---|
| Duck typing | Respond to methods, not check class |
| Convention | snake_case methods, PascalCase classes |
| Blocks everywhere | Yield to blocks for callbacks and iteration |
| Open classes | Extend existing classes carefully |
| POLA | Principle of Least Astonishment |
Quick Start
# Create a new gem skeleton
bundle gem myapp
# Install dependencies
bundle install
# Run tests
bundle exec rspec
bundle exec rake test # Minitest
# Run linter
bundle exec rubocop
# Interactive console
bundle exec irb -r ./lib/myapp
Patterns
Pattern 1: Error Handling
module MyApp
# Define a hierarchy of custom errors
class Error < StandardError; end
class NotFoundError < Error; end
class ValidationError < Error
attr_reader :field
def initialize(field, message)
@field = field
super("Validation failed on #{field}: #{message}")
end
end
class AuthenticationError < Error; end
end
# Raise and rescue with specificity
class UserService
def find!(id)
user = repository.find(id)
raise MyApp::NotFoundError, "User #{id} not found" unless user
user
end
def create(params)
validate!(params)
repository.save(User.new(params))
rescue MyApp::ValidationError => e
logger.warn("Validation failed: #{e.message}")
raise
rescue StandardError => e
logger.error("Unexpected error: #{e.message}")
raise MyApp::Error, "Failed to create user: #{e.message}"
end
private
def validate!(params)
raise MyApp::ValidationError.new(:email, "is required") if params[:email].nil?
raise MyApp::ValidationError.new(:email, "is invalid") unless params[:email].match?(URI::MailTo::EMAIL_REGEXP)
end
end
# Ensure cleanup with ensure
def with_temp_file
file = Tempfile.new("myapp")
yield file
ensure
file&.close
file&.unlink
end
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 · 400 lines · 46 tokens per session scan A b31de47d01df
ruby-development is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 2,533 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
rubyllm
Build and maintain Ruby or Rails applications with the RubyLLM AI framework. Use for chats, agents, tools, MCP servers, structured output, judgments, evaluations, media generation, transcription, OCR, moderation, embeddings, reranking, tracing, Rails integration, and RubyLLM upgrades; not for contributing to the…
new
Create a new project to start development quickly.
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…
dhh-rails-style
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals…
ruby-patterns
Ruby/Rails: blocks, metaprogramming, ActiveRecord, Sidekiq, RSpec, Sorbet, Hanami. Triggers: Ruby, Rails, ActiveRecord, Sidekiq, RSpec, Gemfile, bundler, Hanami, Sorbet.
ruby-idioms
Modern Ruby (3.x) idioms: pattern matching, keyword arguments, immutable data structures, error hierarchies, and RSpec testing. Use when writing, modifying, or reviewing Ruby scripts, gems, or business logic. Pair with rails-idioms for Rails applications.