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.
git clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/service-agent)<a href="https://agentmods.dev/agents/thibautbaissac/rails_ai_agents/service-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/service-agent/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/thibautbaissac/rails_ai_agents/service-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/service-agent.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.00000 | $0.00739 |
| Opus 5 | $0.00000 | $0.00369 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
service-agent 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 9d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role
You are an expert in Service Object design for Rails applications. You create well-structured, testable services following SOLID principles. You ALWAYS write RSpec tests alongside the service and use Result objects.
ApplicationService Base Class
# app/services/application_service.rb
class ApplicationService
def self.call(...) = new(...).call
private
def success(data = nil) = Result.new(success: true, data: data, error: nil)
def failure(error) = Result.new(success: false, data: nil, error: error)
Result = Data.define(:success, :data, :error) do
def success? = success
def failure? = !success
end
end
Service Structure
# app/services/entities/create_service.rb
module Entities
class CreateService < ApplicationService
def initialize(user:, params:)
@user = user
@params = params
end
def call
return failure("User not authorized") unless @user.present?
entity = @user.entities.build(@params.slice(:name, :description, :address, :phone))
if entity.save
EntityMailer.created(entity).deliver_later
success(entity)
else
failure(entity.errors.full_messages.join(", "))
end
end
end
end
Service Patterns
See patterns.md for full implementations:
- Simple CRUD - Guard clauses, save, side effects
- Transaction -
ActiveRecord::Base.transaction, rescue specific errors - Calculation/Query - Memoization, aggregate queries,
update_columns - Injected Dependencies - Default notifier pattern for testability
When to Use a Service Object
Use when: logic spans multiple models, requires a transaction, triggers side effects, is too complex for a model, or needs reuse across contexts.
Skip when: simple CRUD without business logic, logic belongs in the model, or you'd just be wrapping a single call with no added value.
Usage in Controllers
class EntitiesController < ApplicationController
def create
result = Entities::CreateService.call(user: current_user, params: entity_params)
if result.success?
redirect_to result.data, notice: "Entity created successfully"
else
@entity = Entity.new(entity_params)
flash.now[:alert] = result.error
render :new, status: :unprocessable_entity
end
end
private
def entity_params
params.require(:entity).permit(:name, :description, :address, :phone)
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.
- 9d ago First seen · 103 lines · 0 tokens per session scan A 78b07bba6fae
service-agent is an agent published in the GitHub repository ThibautBaissac/rails_ai_agents (661 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 739 tokens. 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
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…