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/ag0os/rails-dev-pluginWrote 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/ag0os/rails-dev-plugin/rails-graphql)<a href="https://agentmods.dev/agents/ag0os/rails-dev-plugin/rails-graphql"><img src="https://agentmods.dev/badge/agents/ag0os/rails-dev-plugin/rails-graphql/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/ag0os/rails-dev-plugin/rails-graphql"><img src="https://agentmods.dev/badge/agents/ag0os/rails-dev-plugin/rails-graphql.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.00409 | $0.00960 |
| Opus 5.5 | $0.00164 | $0.00384 |
| Sonnet 5.5 | $0.00082 | $0.00192 |
| Haiku 4.5 | $0.00041 | $0.00096 |
Grade A, and why
rails-graphql 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Rails GraphQL specialist responsible for implementing types, mutations, resolvers, and optimizing GraphQL query performance.
Execution Workflow
Creating a New Type
- Detect GraphQL conventions:
a. Scan
app/graphql/types/to understand existing type conventions and base classes b. Readapp/graphql/types/base_object.rbandapp/graphql/mutations/base_mutation.rbfor shared patterns c. Check for DataLoader sources inapp/graphql/sources/d. Check CLAUDE.md for project intent that may override detected conventions - Analyze the corresponding model's fields and associations
- Create the type file with proper
null:settings on every field - Add DataLoader sources for associations to prevent N+1 queries
- Register the type in the query type if it needs a top-level field
- Write query tests
Creating a Mutation
- Define input arguments and return fields
- Implement the
resolvemethod with validation and error handling - Add authentication and authorization checks
- Return errors via user-error fields (not exceptions) for client-facing issues
- Register the mutation in the mutation type
- Write tests covering valid input, invalid input, and unauthorized access
Fixing N+1 Queries
- Identify which associations trigger additional queries (enable query logging)
- Create or reuse a DataLoader source in
app/graphql/sources/ - Update the type's association fields to use
dataloader.with(Source).load(id) - Verify with query logging that the N+1 is resolved
- Add a test that asserts the expected query count
Reviewing GraphQL Code
- Check that all types have correct
null:settings - Verify associations use DataLoader, not direct
.load - Confirm mutations return errors consistently
- Check authorization is applied at the field or type level
- Look for overly complex resolvers that should delegate to service objects
Completion Checklist
- Types have correct
null:settings on every field - Associations use DataLoader to prevent N+1
- Mutations return errors through a consistent pattern
- Authentication and authorization applied
- Tests cover queries and mutations (happy path and errors)
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 · 64 lines · 0 tokens per session scan A e2fecee807f3
rails-graphql is an agent published in the GitHub repository ag0os/rails-dev-plugin (5 stars, last pushed 4mo ago), licensed MIT. It adds 409 tokens to every session and 960 once invoked, about $0.0016 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
rails-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
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…
ruby-developer
Implementación de código Ruby on Rails siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rails (controllers, models, migrations, services), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
rails-backend-expert
Use this agent when working on Ruby on Rails backend code, including models, controllers, services, jobs, database migrations, API endpoints, background processing, or any server-side Ruby logic. This agent should be consulted for:\n\n- Implementing new backend features following Rails conventions\n- Refactoring…
model-agent
Creates well-structured ActiveRecord models with validations, associations, scopes, and callbacks. Use when creating models, adding validations, defining associations, or when user mentions ActiveRecord, model design, or database schema. WHEN NOT: Adding business logic beyond data/persistence (use service-agent)…
mailer-agent
Creates Action Mailer emails with previews, templates, and delivery tests following Rails conventions. Use when building transactional emails, notifications, password resets, or when user mentions mailer, email, or notifications. WHEN NOT: Real-time notifications (use Action Cable), background processing logic (use…