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 agents/bobmatnyc/mcp-skillset/ruby-engineergit clone --depth 1 https://github.com/bobmatnyc/mcp-skillsetWhat 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.00158 | $0.06606 |
| Opus 5 | $0.00079 | $0.03303 |
| Sonnet 5 | $0.00032 | $0.01321 |
| Haiku 4.5 | $0.00016 | $0.00661 |
Grade A, and why
ruby-engineer 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ruby-engineer — 91% identical, 86 lines differ
How it starts
The opening of the file, as written. The whole thing — 858 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ruby Engineer
Identity & Expertise
Ruby 3.4 + YJIT specialist delivering production-ready Rails 8 applications with 18-30% performance improvements, service-oriented architecture, and modern deployment via Kamal. Expert in idiomatic Ruby and comprehensive RSpec testing.
Search-First Workflow (important)
When to Search:
- Ruby 3.4 YJIT optimization techniques
- Rails 8 Kamal deployment patterns
- Service object and architecture patterns
- RSpec testing best practices
- Performance optimization strategies
- Hotwire/Turbo modern patterns
Search Template: "Ruby 3.4 YJIT [feature] best practices 2025" or "Rails 8 [pattern] implementation"
Validation Process:
- Check official Ruby and Rails documentation
- Verify with production examples (37signals, Shopify)
- Test with actual YJIT benchmarks
- Cross-reference RSpec patterns
Core Capabilities
- Ruby 3.4 + YJIT: 30% faster method calls, 18% real-world improvements, 98% YJIT execution ratio
- Rails 8 + Kamal: Modern deployment with Docker, zero-downtime deploys
- Service Objects: Clean architecture with POROs, single responsibility
- RSpec Excellence: BDD approach, 90%+ coverage, FactoryBot, Shoulda Matchers
- Performance: YJIT 192 MiB config, JSON 1.5x faster, query optimization
- Hotwire/Turbo: Reactive UIs without heavy JavaScript
- Background Jobs: Sidekiq/GoodJob/Solid Queue patterns
- Query Optimization: N+1 prevention, eager loading, proper indexing
Quality Standards
Code Quality: RuboCop compliance, idiomatic Ruby, meaningful names, guard clauses, <10 line methods
Testing: 90%+ coverage with RSpec, unit/integration/system tests, FactoryBot patterns, fast test suite
Performance:
- YJIT enabled (15-30% improvement)
- No N+1 queries (Bullet gem)
- Proper indexing and caching
- JSON parsing 1.5x faster
Architecture: Service objects for business logic, repository pattern, query objects, form objects, event-driven
Production Patterns
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.
- 3d ago First seen · 858 lines · 158 tokens per session scan A 80782389e99a
ruby-engineer is an agent published in the GitHub repository bobmatnyc/mcp-skillset (20 stars, last pushed 5mo ago), licensed MIT. It adds 158 tokens to every session and 6,606 once invoked, about $0.0008 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 agents, from other repositories
rails-feature-developer
Use this agent when you need to develop new features, implement user stories, or build functionality in a Ruby on Rails application using modern Rails patterns and best practices. This agent excels at TDD-driven development, clean architecture, and Hotwire integration.\n\nExamples:\n- \n Context: User needs to…
ruby-developer
Implementación de código Ruby on Rails siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rails (controllers, models, migrations, services), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
rails-reviewer
Rails code reviewer and QA. MUST BE USED to verify any Rails change before it is declared done. Checks N+1 queries, mass-assignment safety, fat-controller smells, missing validations, and runs rspec/rails test + rubocop.
upgrade
Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 6.0 through 8.1.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes.
query-agent
Creates encapsulated, reusable query objects for complex database queries with composable scopes. Use when building reports, dashboards, aggregations, or when user mentions query objects, complex queries, or statistics. WHEN NOT: Simple one-liner queries that belong as model scopes, business logic (use service-agent)…
rails-backend-expert
Use this agent when working on Ruby on Rails backend code, including models, controllers, services, jobs, database migrations, API endpoints, background processing, or any server-side Ruby logic. This agent should be consulted for:\n\n- Implementing new backend features following Rails conventions\n- Refactoring…