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/igmarin/rails-ai-bridgeWrote 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/instructions/igmarin/rails-ai-bridge/rails-mcp-tools)<a href="https://agentmods.dev/instructions/igmarin/rails-ai-bridge/rails-mcp-tools"><img src="https://agentmods.dev/badge/instructions/igmarin/rails-ai-bridge/rails-mcp-tools/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/instructions/igmarin/rails-ai-bridge/rails-mcp-tools"><img src="https://agentmods.dev/badge/instructions/igmarin/rails-ai-bridge/rails-mcp-tools.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.00519 | $0.00519 |
| Opus 5.5 | $0.00208 | $0.00208 |
| Sonnet 5.5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
rails-ai-bridge rails-mcp-tools.instructions.md 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.
What it actually says
MCP Tool Reference
This project has MCP tools for live introspection.
Start with detail:"summary", then drill into specifics.
Anti-hallucination rules
- Verify before you write (column, association, route, helper, gem).
- Mark assumptions with
[ASSUMPTION]. Silent guesses are forbidden. - This app is not average Rails. Query conventions and gems before scaffolding.
- Check the inheritance chain (filters, concerns, STI) before editing a controller or model.
- Empty tool output is information, not permission to invent.
- Re-query after writes. Stale tool output lies.
Detail levels (schema, routes, models, controllers)
summary— names + counts (default limit: 50)standard— names + key details (default limit: 15, this is the default)full— everything including indexes, FKs (default limit: 5)
rails_get_schema
Params: table, detail, limit, offset, format
rails_get_schema(detail:"summary")— all tables with column countsrails_get_schema(table:"users")— full detail for one tablerails_get_schema(detail:"summary", limit:20, offset:40)— paginate
rails_get_model_details
Params: model, detail
rails_get_model_details(detail:"summary")— list all model namesrails_get_model_details(model:"User")— full associations, validations, scopes
rails_get_routes
Params: controller, detail, limit, offset
rails_get_routes(detail:"summary")— route counts per controllerrails_get_routes(controller:"users")— routes for one controller
rails_get_controllers
Params: controller, detail
rails_get_controllers(detail:"summary")— names + action countsrails_get_controllers(controller:"UsersController")— actions, filters, params
Other tools
rails_get_config— cache store, session, timezone, middlewarerails_get_test_info— test framework, factories/fixtures, CI configrails_get_gems— notable gems categorized by functionrails_get_conventions— architecture patterns, directory structurerails_search_code(pattern:"regex", file_type:"rb", max_results:20)— codebase search
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 · 50 lines · 519 tokens per session scan A dda10ad674ec
rails-ai-bridge rails-mcp-tools.instructions.md is an instructions file published in the GitHub repository igmarin/rails-ai-bridge (16 stars, last pushed yesterday), licensed MIT. It adds 519 tokens to every session, about $0.0021 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-15.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.