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 ombulabs/claude-code_rails-load-defaults-skill --skill rails-load-defaultsgit clone --depth 1 https://github.com/ombulabs/claude-code_rails-load-defaults-skillWrote 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/ombulabs/claude-code_rails-load-defaults-skill/rails-load-defaults)<a href="https://agentmods.dev/skills/ombulabs/claude-code_rails-load-defaults-skill/rails-load-defaults"><img src="https://agentmods.dev/badge/skills/ombulabs/claude-code_rails-load-defaults-skill/rails-load-defaults.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 82 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
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.00120 | $0.02103 |
| Opus 5 | $0.00060 | $0.01052 |
| Sonnet 5 | $0.00024 | $0.00421 |
| Haiku 4.5 | $0.00012 | $0.00210 |
Grade A, and why
rails-load-defaults 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 8d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails load_defaults Upgrade Skill
This skill guides the incremental upgrade of config.load_defaults in a Rails
application. The process walks through each config introduced in a new Rails
version, one at a time, so the user can test each change in isolation.
Overview
When a Rails app has a load_defaults version lower than its Rails version,
there are framework default configs that need to be adopted. This skill:
- Detects the current
load_defaultsversion - Determines the next target version
- Generates the
new_framework_defaults_X_Y.rbinitializer with all configs commented - Walks through each config one by one, analyzing the codebase to recommend values
- Waits for the user to test/commit each change before moving to the next
- Consolidates into
config/application.rbwhen all configs are done
Step 1: Detect Current State
Read config/application.rb and look for:
config.load_defaults X.Y
Also check if a config/initializers/new_framework_defaults_*.rb file already
exists (the user may be mid-upgrade).
Report to the user:
- Current
load_defaultsversion - Current Rails version (from Gemfile.lock)
- Which version transitions are needed (e.g., 6.1 → 7.0 → 7.1 → 7.2)
Step 2: Load Version Config Reference
Read the appropriate config reference file for the target version:
- 5.0:
configs/5_0.yml - 5.1:
configs/5_1.yml - 5.2:
configs/5_2.yml - 6.0:
configs/6_0.yml - 6.1:
configs/6_1.yml - 7.0:
configs/7_0.yml - 7.1:
configs/7_1.yml - 7.2:
configs/7_2.yml - 8.0:
configs/8_0.yml - 8.1:
configs/8_1.yml
Each config file contains entries organized into tiers with lookup patterns and decision trees for each config.
Step 3: Create the Initializer File
If no new_framework_defaults_X_Y.rb exists yet, copy the template from
the templates/ directory into the app's config/initializers/:
- 5.0: Copy
templates/new_framework_defaults_5_0.rb→config/initializers/new_framework_defaults_5_0.rb - 5.1: Copy
templates/new_framework_defaults_5_1.rb→config/initializers/new_framework_defaults_5_1.rb - 5.2: Copy
templates/new_framework_defaults_5_2.rb→config/initializers/new_framework_defaults_5_2.rb - 6.0: Copy
templates/new_framework_defaults_6_0.rb→config/initializers/new_framework_defaults_6_0.rb - 6.1: Copy
templates/new_framework_defaults_6_1.rb→config/initializers/new_framework_defaults_6_1.rb - 7.0: Copy
templates/new_framework_defaults_7_0.rb→config/initializers/new_framework_defaults_7_0.rb - 7.1: Copy
templates/new_framework_defaults_7_1.rb→config/initializers/new_framework_defaults_7_1.rb - 7.2: Copy
templates/new_framework_defaults_7_2.rb→config/initializers/new_framework_defaults_7_2.rb - 8.0: Copy
templates/new_framework_defaults_8_0.rb→config/initializers/new_framework_defaults_8_0.rb - 8.1: Copy
templates/new_framework_defaults_8_1.rb→config/initializers/new_framework_defaults_8_1.rb
What ships with it
21 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.
- configs/5_0.yml 6.8 KB
- configs/5_1.yml 3.0 KB
- configs/5_2.yml 5.8 KB
- configs/6_0.yml 7.3 KB
- configs/6_1.yml 13 KB
- configs/7_0.yml 17 KB
- configs/7_1.yml 23 KB
- configs/7_2.yml 6.5 KB
- configs/8_0.yml 5.7 KB
- configs/8_1.yml 13 KB
- templates/cookie_rotator.rb 1.5 KB runs code
- templates/new_framework_defaults_5_0.rb 1.8 KB runs code
- templates/new_framework_defaults_5_1.rb 875 B runs code
- templates/new_framework_defaults_5_2.rb 2.1 KB runs code
- templates/new_framework_defaults_6_0.rb 2.9 KB runs code
- templates/new_framework_defaults_6_1.rb 3.3 KB runs code
- templates/new_framework_defaults_7_0.rb 7.4 KB runs code
- templates/new_framework_defaults_7_1.rb 12 KB runs code
- templates/new_framework_defaults_7_2.rb 3.1 KB runs code
- templates/new_framework_defaults_8_0.rb 1.3 KB runs code
- templates/new_framework_defaults_8_1.rb 3.1 KB runs code
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.
- 8d ago First seen · 213 lines · 120 tokens per session scan A 6ec1d57f7669
rails-load-defaults is a skill published in the GitHub repository ombulabs/claude-code_rails-load-defaults-skill (17 stars, last pushed 18d ago), licensed MIT. It adds 120 tokens to every session and 2,103 once invoked, about $0.0006 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-30.
Other skills, from other repositories
dual-boot
Sets up and manages dual-boot Ruby and Rails environments using the nextrails gem. Helps configure Gemfile for running two versions of Rails, Ruby, or any core dependency simultaneously, set up CI for both versions, use NextRails.next? for version-dependent code, and clean up after the upgrade is complete. Based on…
rails-api-controllers
RESTful API controller patterns for Ruby on Rails. Use when: (1) Building JSON APIs, (2) API versioning, (3) Error handling and status codes, (4) Authentication with tokens/JWT, (5) Rate limiting, (6) CORS configuration, (7) Pagination and filtering, (8) API documentation, (9) Testing API endpoints.
rails-mailers
Use when sending emails - ActionMailer with async delivery via SolidQueue, templates, previews, and testing.
rails-pagination-kaminari
Pagination for Ruby on Rails applications using Kaminari. Use when: (1) Implementing pagination for database records, (2) Building paginated API endpoints, (3) Customizing pagination UI with themes, (4) Handling large datasets efficiently, (5) Creating infinite scroll, (6) Paginating arrays or custom collections, (7)…
rails-controllers
Controller actions, routing, REST conventions, filters, and response handling.
rails-auth-with-devise
Complete authentication setup for Ruby on Rails applications using Devise. Use when: (1) Setting up user authentication in a Rails app, (2) Adding sign in/sign up/sign out functionality, (3) Implementing email confirmation, password recovery, or account locking, (4) Configuring OmniAuth social login, (5) Adding…