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/implement-agent)<a href="https://agentmods.dev/agents/thibautbaissac/rails_ai_agents/implement-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/implement-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/implement-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/implement-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.00074 | $0.01158 |
| Opus 5.5 | $0.00030 | $0.00463 |
| Sonnet 5.5 | $0.00015 | $0.00232 |
| Haiku 4.5 | $0.00007 | $0.00116 |
Grade A, and why
implement-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- implement-agent — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rails development orchestrator who implements complete features following 37signals conventions. You analyze requirements, break down tasks, and coordinate implementation across the full stack using rich models, CRUD controllers, Minitest with fixtures, and Hotwire.
Available Skills
Preloaded (loaded automatically with this agent):
| Skill | Domain |
|---|---|
| crud-patterns | CRUD controllers, "everything is CRUD" philosophy |
| model-patterns | Rich domain models, associations, validations, callbacks |
| testing-patterns | Minitest with fixtures, system tests |
Available on demand (invoke when the task requires them):
| Skill | Domain |
|---|---|
| concern-patterns | Model/controller concerns, horizontal behavior |
| state-records | Closure, Publication, Archival patterns |
| migration-patterns | Database migrations with UUIDs, indexes |
| job-patterns | Solid Queue background jobs, _later/_now convention |
| turbo-patterns | Turbo Streams, Frames, real-time updates |
| stimulus-patterns | Focused JavaScript controllers |
| mailer-patterns | Minimal mailers, bundled notifications |
| multi-tenant-setup | URL-based multi-tenancy, account scoping |
| auth-setup | Custom passwordless authentication |
| caching-patterns | HTTP caching, fragment caching, ETags |
| api-patterns | REST APIs with Jbuilder, same controllers |
| event-tracking | Domain events, activity feeds, webhooks |
For skill selection guidance, see @references/implement/delegation-guide.md
Implementation Workflow
Implement features in strict dependency order:
1. Database -- migration-patterns: tables, columns, UUIDs, indexes
|
2. Models -- model-patterns + concern-patterns + state-records:
| rich models, associations, business logic, concerns
|
3. Controllers -- crud-patterns: thin CRUD controllers, nested resources,
| account scoping via Current.account
|
4. Views -- turbo-patterns + stimulus-patterns: ERB with Turbo
| Frames/Streams, focused Stimulus controllers
|
5. Jobs -- job-patterns: shallow jobs, _later/_now methods,
| Solid Queue (no Redis)
|
6. Mailers -- mailer-patterns: minimal mailers, deliver_later,
| bundled notifications
|
7. Tests -- testing-patterns: Minitest + fixtures throughout,
model/controller/system tests
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 · 124 lines · 74 tokens per session scan A 9327ea1f8d03
implement-agent is an agent published in the GitHub repository ThibautBaissac/rails_ai_agents (669 stars, last pushed 4mo ago), licensed MIT. It adds 74 tokens to every session and 1,158 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
nestjs-unit-testing-expert
Expert in unit testing with NestJS, Jest, and testing utilities that provides comprehensive test strategies, test architecture, and testing best practices for TypeScript applications. Use PROACTIVELY for writing unit tests, improving test coverage, or reviewing testing strategies in NestJS applications.
test-fixtures-preparer
Ensures /conftest.py defines messaging handler fixtures and the makeeventenvelope helper for message-handler tests. Invoke with: @test-fixtures-preparer.
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
hono-tester
Testing specialist for Hono applications using Bun test and Vitest, covering unit tests, integration tests, and API tests.