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 skills/ag0os/rails-dev-plugin/rails-views-patternsnpx skills add ag0os/rails-dev-plugin --skill rails-views-patternsgit 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/skills/ag0os/rails-dev-plugin/rails-views-patterns)<a href="https://agentmods.dev/skills/ag0os/rails-dev-plugin/rails-views-patterns"><img src="https://agentmods.dev/badge/skills/ag0os/rails-dev-plugin/rails-views-patterns.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.01013 |
| Opus 5 | $0.00039 | $0.00507 |
| Sonnet 5 | $0.00016 | $0.00203 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
rails-views-patterns 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Views Patterns
Follow standard Rails view conventions for ERB templates, partials, layouts, helpers, form_with, and content_for regions. This skill covers only the opinionated and non-obvious additions.
Applies on the html delivery axis (Axis B, rails-stack-profiles). On the api axis there are no app views — use rails-api-patterns instead.
See patterns.md for detailed examples.
Quick Reference
| Area | Key Rule | Anti-Pattern |
|---|---|---|
| Partials | Extract reusable components | Duplicated HTML across views |
| Collections | Always use render collection: |
Manual loops with each |
| Caching | Fragment cache expensive renders | No caching on collection renders |
| Accessibility | Semantic HTML + ARIA | <div> soup without roles |
| Logic | Presenter or helper for complex logic | Conditionals in templates |
Core Principles
- Views are for presentation only -- no queries, no mutations, no business logic
- Semantic HTML5 -- use
<header>,<nav>,<main>,<article>,<section>,<aside>instead of generic<div>wrappers - Always
render collection:-- nevereach+renderinside the loop (performance + enables collection caching) - Cache aggressively -- fragment caching with
cached: trueon collections, Russian-doll nesting for parent/child
Presenter Objects and ViewComponents
Where complex view logic goes is governed by an orthogonal project fact, not an architecture axis: whether the view_component gem is installed. Read it from the project-conventions fingerprint (Frontend category).
view_componentgem present: use ViewComponents — see patterns.md.- No
view_componentgem: extract complex view logic into plain Ruby presenter objects.
# app/presenters/dashboard_presenter.rb
class DashboardPresenter
attr_reader :user, :period
def initialize(user:, period: Date.current.all_month)
@user = user
@period = period
end
def grouped_activities
user.activities.where(date: period).group_by(&:category).sort_by { |cat, _| cat.position }
end
def empty? = user.activities.where(date: period).none?
def title = "#{user.name}'s Dashboard"
end
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 100 lines · 79 tokens per session scan A 0641d607b346
rails-views-patterns is a skill published in the GitHub repository ag0os/rails-dev-plugin (5 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,013 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-31.
Other skills, from other repositories
rails-expert
Rails 7+ specialist that optimizes Active Record queries with includes/eagerload, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building…
contributing
Contribute to RubyLLM - set up the repo, run and record specs, add providers or chat options, work on the Rails integration, and edit docs. Use when fixing a bug, building a feature, writing specs, or changing documentation in the RubyLLM codebase.
rails-conventions
Rootstrap Rails conventions. Use when writing, reviewing, or editing any Rails code — controllers, models, migrations, routes, views, mailers, initializers, locale files, or Rails config. Covers routing, ActiveRecord, migrations, i18n, time zones, mailers, assets, Bundler groups, and logging.
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
rails-upgrade
Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 2.3 through 8.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes. Based on FastRuby.io methodology and "The…
ruby-conventions
Rootstrap Ruby style conventions. Use when writing, reviewing, or editing any Ruby source file (.rb, .rake, Gemfile, Rakefile, .gemspec, config.ru) to ensure code follows the Rootstrap Ruby style guide — covers layout, syntax, naming, classes/modules, exceptions, collections, strings, regexes, metaprogramming, and…