1005-service-objects

A standard for service objects in Ruby on Rails, a web framework for Ruby. A service object is a small class that performs one focused business operation outside a controller or model.

In plain words
What is it for?
Use it when creating or changing Rails service classes, including naming them, accepting inputs, validating data, handling errors, documenting methods, and returning results.
Why use it?
It keeps business logic focused, testable, and consistent instead of spreading it across unrelated parts of the application.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/andyw8/rails_rules/1005-service-objects
Clone the repo
git clone --depth 1 https://github.com/andyw8/rails_rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 672 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00672
Opus 5 $0.00000 $0.00336
Sonnet 5 $0.00000 $0.00134
Haiku 4.5 $0.00000 $0.00067

Measured 2d ago against content hash b2ecd7b6b4ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

1005-service-objects 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.

lib/generators/rails_rules/templates/1005-service-objects.mdc · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Service Object Standards

Context

  • In Ruby on Rails 8.0 service objects
  • Used to encapsulate business logic
  • Follows PORO (Plain Old Ruby Object) principles

Requirements

  • Create service objects in app/services directory
  • Name services with verb + noun format ending with "Service" (e.g., CreateUserService)
  • Use class Service::ClassName instead of nested module class
  • Use initialize method to accept parameters
  • Include YARD documentation for all methods
  • Implement a run (or call, perform, execute) method that performs the service's main action
  • Return a result object or the expected return value
  • Keep service objects focused on a single responsibility
  • Validate parameters in initialize or a separate validate method
  • Handle errors gracefully, either through exceptions or a result object
  • Make services testable with Minitest
  • Only modify state through explicit interfaces, not by relying on side effects

Examples

Service for creating a new user with account

@example

service = CreateUserService.new(email: "[email protected]", name: "Test User")

user = service.run

class CreateUserService

Initialize the service with user attributes

@param [Hash] attributes The user attributes

@option attributes [String] :email User's email

@option attributes [String] :name User's name

@option attributes [String] :password User's password

def initialize(attributes) @attributes = attributes @account_name = attributes.delete(:account_name) || "My Account" end

Runs the service to create a user and account

@return [User] The created user

@raise [ActiveRecord::RecordInvalid] If validation fails

def run User.transaction do create_user create_account create_account_user end

@user

end

private

Creates a new user with the provided attributes

@return [User] The new user

def create_user @user = User.create!(@attributes) end

Creates a new account for the user

@return [Account] The new account

def create_account @account = Account.create!(name: @account_name, owner: @user) end

Creates the account user relationship

@return [AccountUser] The account user relationship

def create_account_user AccountUser.create!( account: @account, user: @user, admin: true ) end end

</example>

Read the full file on GitHub · 130 lines

Changes

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.

  1. 2d ago First seen · 130 lines · 0 tokens per session scan A b2ecd7b6b4ad

Subscribe to this mod's changes

1005-service-objects is a cursor rule published in the GitHub repository andyw8/rails_rules (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 672 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-31.