Borrowing it
Nothing to install: this file belongs to levifig/rails-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/levifig/rails-instructions/main/.github/instructions/rails-views.instructions.mdgit clone --depth 1 https://github.com/levifig/rails-instructionsWrote 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/levifig/rails-instructions/rails-views)<a href="https://agentmods.dev/instructions/levifig/rails-instructions/rails-views"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-views/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/levifig/rails-instructions/rails-views"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-views.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.01037 | $0.01037 |
| Opus 5.5 | $0.00415 | $0.00415 |
| Sonnet 5.5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
rails-instructions rails-views.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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Views and Helpers Guide
Core Philosophy
- Keep views simple and logic-free
- Use helpers for presentation logic only
- Leverage Rails' built-in view helpers
- Follow semantic HTML principles
- Optimize for readability and maintainability
View Architecture Principles
- Separate presentation from business logic completely
- Use partials for reusable view components
- Keep views focused on displaying data
- Implement proper HTML semantics
- Design for progressive enhancement
Helper Organization
- Keep helpers focused on specific presentation tasks
- Group related helpers in dedicated modules
- Use ApplicationHelper for truly global helpers
- Document complex helper methods
- Test helpers with various input scenarios
Rails Helper Usage
- Prefer Rails helpers over raw HTML
- Use semantic Rails form helpers
- Leverage Rails' built-in formatting helpers
- Implement proper escaping for security
- Follow Rails conventions for helper naming
Partial Best Practices
- Name partials with leading underscore
- Keep partials small and focused
- Pass locals explicitly for clarity
- Avoid instance variables in partials
- Document partial requirements
Form Design Principles
- Use
form_withfor all forms - Implement proper form accessibility
- Add appropriate ARIA labels
- Use Rails form builders consistently
- Handle errors at the field level
Asset Management
- Use Rails asset helpers for all assets
- Implement proper image alt texts
- Leverage asset fingerprinting
- Configure CDN for production assets
- Optimize images before serving
Internationalization
- Extract all text to locale files
- Use Rails I18n helpers consistently
- Design views for text expansion
- Handle pluralization properly
- Test with multiple locales
Performance Optimization
- Use fragment caching for expensive views
- Implement Russian doll caching
- Avoid N+1 queries in views
- Lazy load below-fold content
- Profile view rendering times
JavaScript Integration
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 · 217 lines · 1,037 tokens per session scan A 217eecf1896d
rails-instructions rails-views.instructions.md is an instructions file published in the GitHub repository levifig/rails-instructions (56 stars, last pushed 1y ago), licensed MIT. It adds 1,037 tokens to every session, about $0.0041 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-30.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.