Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slbug/claude-ruby-grape-rails/plugin install ruby-grape-railsWrote 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/slbug/claude-ruby-grape-rails/iron-laws)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/iron-laws"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/iron-laws.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.1 | $0.00053 | $0.00914 |
| Opus 5 | $0.00026 | $0.00457 |
| Sonnet 5 | $0.00011 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
iron-laws 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 7d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iron Laws
Overview
These 22 rules are NEVER violated. If code would violate them, STOP and explain before proceeding.
Active Record (7 laws)
- Decimal for Money — NEVER use float for money — use decimal or integer (cents)
- Parameterized Queries — ALWAYS use parameterized queries — never interpolate user input into SQL strings
- Eager Loading — USE includes/preload for associations — avoids N+1 queries
- Commit-Safe Enqueueing in Active Record — IN Active Record code, use after_commit not after_save when enqueueing jobs that depend on committed data
- Transaction Boundaries — WRAP multi-step operations in transactions — use ActiveRecord::Base.transaction
- No Validation Bypass — NO update_columns, update_column, or save(validate: false) in normal flows
- No default_scope — NO default_scope — use explicit named scopes only
Sidekiq (4 laws)
- Idempotent Jobs — Jobs MUST be idempotent — safe to retry
- JSON-Safe Arguments — Args use JSON-safe types only — no symbols, no Ruby objects, no procs
- No ORM Objects in Args — NEVER store ORM objects in args — store IDs, not records
- Commit-Safe Enqueueing — ALWAYS enqueue jobs after commit using the active ORM or transaction hook — not after_save or inline before commit
Security (4 laws)
- No Ruby Eval — NO Ruby
eval/instance_eval/class_evalwith user input — code injection vulnerability. Shellevalof trusted helper output is out of scope - Explicit Authorization — AUTHORIZE in EVERY controller action — do not trust before_action alone
- No Unsafe HTML — NEVER use html_safe or raw with untrusted content — XSS vulnerability
- No SQL Concatenation — NO SQL string concatenation — always use parameterized queries
Ruby (3 laws)
- method_missing Requires respond_to_missing? — NO method_missing without respond_to_missing? — breaks introspection
- Supervise Background Processes — SUPERVISE ALL BACKGROUND PROCESSES — use proper process managers in production
- No Rescue Exception — DON'T rescue
Exception(inbegin/rescueor Railsrescue_from) — catchesSystemExit/SignalException. Barerescuedefaults toStandardError, not a Law 18 violation.
What ships with it
3 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.
- 7d ago First seen · 76 lines · 53 tokens per session scan A 63b850d568f9
iron-laws is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 914 once invoked, about $0.0003 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
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…