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 skills add igmarin/rails-agent-skills --skill apply-code-conventionsgit clone --depth 1 https://github.com/igmarin/rails-agent-skillsWrote 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/igmarin/rails-agent-skills/apply-code-conventions)<a href="https://agentmods.dev/skills/igmarin/rails-agent-skills/apply-code-conventions"><img src="https://agentmods.dev/badge/skills/igmarin/rails-agent-skills/apply-code-conventions/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/skills/igmarin/rails-agent-skills/apply-code-conventions"><img src="https://agentmods.dev/badge/skills/igmarin/rails-agent-skills/apply-code-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.01292 |
| Opus 5.5 | $0.00023 | $0.00517 |
| Sonnet 5.5 | $0.00012 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
apply-code-conventions 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 25d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Code Conventions
Style source of truth: Style and formatting defer to the project's configured linter(s). This skill adds non-style behavior and architecture guidance only. For Hotwire + Tailwind specifics, see apply-stack-conventions.
Quick Reference
| Topic | Rule |
|---|---|
| Principles | DRY, YAGNI, PORO where it helps, CoC, KISS |
| Comments / tags | Explain why; tagged notes need actionable context |
| Logging | One verified message argument (usually a JSON hash); no interpolation; include a redacted backtrace on errors |
| Deep stacks | Chain apply-stack-conventions → domain skills (services, jobs, RSpec) |
HARD-GATE
TESTS GATE IMPLEMENTATION:
When this skill guides new behavior, the tests gate still applies:
PRD → TASKS → TEST (write, run, fail) → IMPLEMENTATION → …
No implementation code before a failing test. See write-tests.
Core Process
When reviewing or refactoring Rails code, follow this sequence. Each step maps to a required checkpoint in your output.
- Run linter — Detect config (e.g.
.rubocop.ymlor.standard.yml), run the appropriate tool, note absence if none found. Output: linter detected (or absent); style defers to it. - Apply area-specific rules — Check path patterns and apply targeted guidance from the Apply by area table. Output: concrete per-path recommendations for every relevant changed file.
- Verify tests gate — Confirm failing tests exist before any new behavior. Output: failing spec, run command, expected failure, minimal implementation step, passing rerun.
- Enforce structured logging — Ensure all
Rails.loggercalls use the installed logger's verified single-message interface; include anevent:field and redacted backtrace for errors. Output: apply structured logging rules from Sub-Rules below. - Enforce comment discipline — Ensure all tags (
TODO:,FIXME:) have actionable context (owner, ticket). Output: apply comment discipline rules from Sub-Rules below. - Chain to specialised skills — Use the Integration table to pull in deeper guidance (security, jobs, specs) as needed.
What ships with it
2 files 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.
- 25d ago Changed · -1 lines 1bcf9d4ace60
- 1mo ago Changed · -6 lines 5a28510e3a27
- 1mo ago First seen · 111 lines · 58 tokens per session scan A d24b5d23bab6
apply-code-conventions is a skill published in the GitHub repository igmarin/rails-agent-skills (28 stars, last pushed 26d ago), licensed MIT. It adds 58 tokens to every session and 1,292 once invoked, about $0.0002 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 skills, from other repositories
simplify
Simplifies and refines Ruby on Rails code following 37signals patterns and the One Person Framework philosophy, while preserving exact functionality. Focuses on recently modified code unless instructed otherwise. Use this skill when simplifying or refactoring Rails code, reviewing recently written Rails code for…
sgcop-setup
A setup guide for adding the sgcop Ruby and Rails code-checking rules to a project. RuboCop is a tool that finds style and quality problems in Ruby code.
gem-docs-review
Harvests offline documentation (README, CHANGELOG, public API) for every gem in a Ruby/Rails project's Gemfile.lock into a local cache, tracks gem versions in a manifest, and refreshes only gems whose version changed. Then reviews a git diff or pull request against that cache to surface (a) gem-upgrade impact …
gemtracker
Analyze Ruby gem dependencies, vulnerabilities, outdated packages, maintenance health, and insecure gem sources with the gemtracker CLI. Use when asked to audit Ruby gems, check Gemfile.lock security, review dependency health, or run gemtracker.
rubocop-and-code-quality
Code-quality tooling for Rails — RuboCop with rubocop-rails / rubocop-performance / rubocop-rspec / rubocop-threadsafety extensions, the rubocop-rails-omakase preset (DHH's defaults, shipped with Rails 8), SimpleCov coverage with branch coverage + CI threshold, erblint for ERB templates, RBS / Sorbet for optional type…
kieran-rails-reviewer
Reviews Rails code with an extremely high quality bar for conventions, clarity, and maintainability. Use after implementing features, modifying code, or creating new Rails components.