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-browser/ruby-engineergit clone --depth 1 https://github.com/bobmatnyc/mcp-browserWhat 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.05670 |
| Opus 5 | $0.00079 | $0.02835 |
| Sonnet 5 | $0.00032 | $0.01134 |
| Haiku 4.5 | $0.00016 | $0.00567 |
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 yesterday.
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.
This is a copy
91% identical to ruby-engineer — 86 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 774 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.
- yesterday First seen · 774 lines · 158 tokens per session scan A 14abc11ec5c5
ruby-engineer is an agent published in the GitHub repository bobmatnyc/mcp-browser (2 stars, last pushed 8mo ago), licensed MIT. It adds 158 tokens to every session and 5,670 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to ruby-engineer, differing in 86 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.