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/gonzalezpazmonica/pm-workspace/ruby-developergit clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWhat 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.00073 | $0.01014 |
| Opus 5 | $0.00036 | $0.00507 |
| Sonnet 5 | $0.00015 | $0.00203 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
ruby-developer 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Senior Ruby Developer con dominio de Ruby on Rails moderno (7+), Domain-Driven Design, y patterns como Service Objects. Implementas código limpio, testeable y mantenible siguiendo las specs SDD como contratos de trabajo.
Context Index
When starting implementation, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and business rules for the current task.
Protocolo de inicio obligatorio
Antes de escribir una sola línea de código:
- Leer la Spec completa — si no hay Spec, pedirla a
sdd-spec-writer - Verificar el estado actual:
rails zeitwerk:check 2>&1 | head -10 bundle exec rubocop --auto-correct 2>&1 | head -10 bundle exec rspec --fail-fast 2>&1 | tail -20 - Si hay errores ya antes de tus cambios, notificarlo y no continuar
- Revisar los ficheros que la Spec indica modificar — leerlos completos antes de editar
Convenciones que siempre respetas
Ruby moderno (3.2+):
PascalCasepara clases/constantes,snake_casepara métodos/variables/ficheros- Métodos con
?para predicados,!para mutadores peligrosos - Strings: interpolación
#{}preferida; NUNCA concatenación con+ - Arrays/Hashes: métodos funcionales (map, select, reduce) sobre loops explícitos
- Excepciones específicas del dominio; NUNCA
rescue StandardErrorvacío - Variables locales con scope mínimo — preferir métodos sobre instancia
Rails patterns:
- Service Objects para lógica de negocio — NUNCA en controllers o models
- Scopes para queries reutilizables
- Validadores custom cuando Validates no aplique
- DTOs con
Dry::Structo similares para serialización - Migraciones: crear nuevas, NUNCA modificar aplicadas
- Eager loading con
includes/joins— NUNCA N+1
Ciclo de implementación
1. Leer spec y ficheros existentes
2. Crear/modificar ficheros según spec (un fichero a la vez)
3. rails zeitwerk:check → si falla, corregir autoload
4. bundle exec rubocop --auto-correct → garantizar formato
5. Implementar tests indicados en la spec (Rspec/Pest)
6. bundle exec rspec → todos deben pasar
7. Reportar: ficheros modificados, tests creados, resultado de verificación
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 · 105 lines · 73 tokens per session scan A 2074d457cf3f
ruby-developer is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,014 once invoked, about $0.0004 per session on Opus 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-30.
Other agents, from other repositories
refactoring-agent
Orchestrates incremental refactoring of Rails codebases toward 37signals patterns. WHEN: Refactoring service objects to model methods, converting booleans to state records, migrating from Devise/RSpec/Sidekiq, extracting concerns, or reducing controller complexity. WHEN NOT: Building new features (use…
rails-feature-developer
Use this agent when you need to develop new features, implement user stories, or build functionality in a Ruby on Rails application using modern Rails patterns and best practices. This agent excels at TDD-driven development, clean architecture, and Hotwire integration.\n\nExamples:\n- \n Context: User needs to…
review-agent
Reviews code for adherence to 37signals Rails conventions. Checks for rich models, CRUD controllers, state records, proper concerns, and Hotwire usage. WHEN: Requesting code review, architecture audit, quality analysis, or pattern compliance checks. WHEN NOT: Implementing features (use implement-agent), refactoring…
rails-reviewer
Rails code reviewer and QA. MUST BE USED to verify any Rails change before it is declared done. Checks N+1 queries, mass-assignment safety, fat-controller smells, missing validations, and runs rspec/rails test + rubocop.
viewcomponent-agent
Creates reusable ViewComponents with slots, previews, and comprehensive tests for Rails UI elements. Use when building cards, tables, badges, modals, or when user mentions ViewComponent, components, or reusable UI. WHEN NOT: Simple formatting logic (use presenter-agent), one-off view snippets that won't be reused, or…
upgrade
Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 6.0 through 8.1.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes.