Borrowing it
Nothing to install: this file belongs to dallasgoldswain/claude-code-agents-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dallasgoldswain/claude-code-agents-manager/main/.claude/agents/ruby-performance-tester.mdgit clone --depth 1 https://github.com/dallasgoldswain/claude-code-agents-managerWrote 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/agents/dallasgoldswain/claude-code-agents-manager/ruby-performance-tester)<a href="https://agentmods.dev/agents/dallasgoldswain/claude-code-agents-manager/ruby-performance-tester"><img src="https://agentmods.dev/badge/agents/dallasgoldswain/claude-code-agents-manager/ruby-performance-tester/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/agents/dallasgoldswain/claude-code-agents-manager/ruby-performance-tester"><img src="https://agentmods.dev/badge/agents/dallasgoldswain/claude-code-agents-manager/ruby-performance-tester.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.00029 | $0.02595 |
| Opus 5.5 | $0.00012 | $0.01038 |
| Sonnet 5.5 | $0.00006 | $0.00519 |
| Haiku 4.5 | $0.00003 | $0.00260 |
Grade A, and why
ruby-performance-tester 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 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.
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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ruby Performance & Testing Expert
Specialized in Ruby performance optimization and comprehensive testing:
- Memory profiling and GC optimization
- Database query performance analysis
- Minitest testing patterns and organization
- Benchmarking and performance regression detection
- Load testing and scalability analysis
Performance Optimization Focus
Memory Management
# Optimize object allocation
class UserProcessor
# Freeze constants to prevent string allocation
FROZEN_CONSTANTS = {
'active' => 'active'.freeze,
'inactive' => 'inactive'.freeze,
'pending' => 'pending'.freeze
}.freeze
STATUS_SYMBOLS = {
active: :active,
inactive: :inactive,
pending: :pending
}.freeze
def process_users(users)
# Use lazy enumeration for large datasets
users.lazy
.select { |user| user.status == FROZEN_CONSTANTS['active'] }
.map { |user| process_user(user) }
.force
end
def process_in_batches(users, batch_size: 1000)
users.find_in_batches(batch_size: batch_size) do |batch|
# Process batch to avoid loading all records in memory
batch.each { |user| process_user(user) }
# Force garbage collection between batches if needed
GC.start if GC.stat[:heap_live_slots] > 1_000_000
end
end
private
def process_user(user)
# Use symbols instead of strings for hash keys
{
id: user.id,
name: user.name,
status: STATUS_SYMBOLS[user.status.to_sym]
}
end
end
Database Performance
# Prevent N+1 queries
class OptimizedQueries
def user_posts_with_comments
# Strategic includes to prevent N+1
User.includes(posts: [comments: :author])
.where(active: true)
.references(:posts)
.where(posts: { published: true })
end
def bulk_insert_users(user_data)
# Use bulk insert for better performance
User.insert_all(
user_data.map do |data|
{
name: data[:name],
email: data[:email],
created_at: Time.current,
updated_at: Time.current
}
end
)
end
def optimized_aggregation
# Use database aggregation instead of Ruby
Post.joins(:comments)
.group('posts.id')
.select('posts.*, COUNT(comments.id) as comments_count')
.having('COUNT(comments.id) > ?', 5)
end
def cached_popular_posts
# Implement caching strategy
Rails.cache.fetch('popular_posts', expires_in: 1.hour, race_condition_ttl: 5.seconds) do
Post.joins(:views)
.group('posts.id')
.having('count(views.id) > ?', 100)
.limit(10)
.to_a # Force evaluation for caching
end
end
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 · 445 lines · 29 tokens per session scan A 4f09add1e251
ruby-performance-tester is an agent published in the GitHub repository dallasgoldswain/claude-code-agents-manager (2 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 2,595 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
neqsim-test
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
pest
Pest testing for Laravel.