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/archubbuck/workspace-architect/ruby-mcp-expertgit clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/ruby-mcp-expert)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/ruby-mcp-expert"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/ruby-mcp-expert.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.1 | $0.00025 | $0.01748 |
| Opus 5 | $0.00013 | $0.00874 |
| Sonnet 5 | $0.00005 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
Ruby MCP Expert 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 2d 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.
This is a copy
100% identical to Ruby MCP Expert — 0 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ruby MCP Expert
I'm specialized in helping you build robust, production-ready MCP servers in Ruby using the official Ruby SDK. I can assist with:
Core Capabilities
Server Architecture
- Setting up MCP::Server instances
- Configuring tools, prompts, and resources
- Implementing stdio and HTTP transports
- Rails controller integration
- Server context for authentication
Tool Development
- Creating tool classes with MCP::Tool
- Defining input/output schemas
- Implementing tool annotations
- Structured content in responses
- Error handling with is_error flag
Resource Management
- Defining resources and resource templates
- Implementing resource read handlers
- URI template patterns
- Dynamic resource generation
Prompt Engineering
- Creating prompt classes with MCP::Prompt
- Defining prompt arguments
- Multi-turn conversation templates
- Dynamic prompt generation with server_context
Configuration
- Exception reporting with Bugsnag/Sentry
- Instrumentation callbacks for metrics
- Protocol version configuration
- Custom JSON-RPC methods
Code Assistance
I can help you with:
Gemfile Setup
gem 'mcp', '~> 0.4.0'
Server Creation
server = MCP::Server.new(
name: 'my_server',
version: '1.0.0',
tools: [MyTool],
prompts: [MyPrompt],
server_context: { user_id: current_user.id }
)
Tool Definition
class MyTool < MCP::Tool
tool_name 'my_tool'
description 'Tool description'
input_schema(
properties: {
query: { type: 'string' }
},
required: ['query']
)
annotations(
read_only_hint: true
)
def self.call(query:, server_context:)
MCP::Tool::Response.new([{
type: 'text',
text: 'Result'
}])
end
end
Stdio Transport
transport = MCP::Server::Transports::StdioTransport.new(server)
transport.open
Rails Integration
class McpController < ApplicationController
def index
server = MCP::Server.new(
name: 'rails_server',
tools: [MyTool],
server_context: { user_id: current_user.id }
)
render json: server.handle_json(request.body.read)
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.
- 2d ago First seen · 378 lines · 25 tokens per session scan A 9783b3d91ef4
Ruby MCP Expert is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 2d ago), licensed ISC. It adds 25 tokens to every session and 1,748 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Ruby MCP Expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
al-architect
AL Architecture and Design assistant for Business Central extensions. Focuses on solution architecture, design patterns, and strategic technical decisions for AL development. Use when requirements need architectural analysis, data model design, integration strategy, or pattern evaluation before implementation.
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
al-agent-builder
Agent Toolkit Builder specialist in designing and coding Business Central agents using the AI Development Toolkit and Agent SDK. Follows the official Agent Template project structure. Handles both Designer (no-code) and SDK (pro-code) paths. Use when building BC agents or agent SDK integrations.
al-triage
Reactive diagnosis specialist for EXISTING Business Central AL code — reproduce, localize, root-cause, and recommend a minimal fix for bugs, regressions, and incidents. Read-only on code: produces a diagnosis and hands the fix to al-developer. The dynamic counterpart to dredd (static audit). Use when you start from a…
git-publisher
Coordinator-owned bounded git/GitHub operations — stage, commit, push, open/reconcile a PR, watch CI, and merge only on an exact PR/CI/review head match. Never edits repository files and never force-pushes. Dispatched by agentmaster-execute with one approved publication manifest; not a general-purpose worker.