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 ThibautBaissac/rails_ai_agents --skill state-recordsgit clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/state-records)<a href="https://agentmods.dev/skills/thibautbaissac/rails_ai_agents/state-records"><img src="https://agentmods.dev/badge/skills/thibautbaissac/rails_ai_agents/state-records/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/thibautbaissac/rails_ai_agents/state-records"><img src="https://agentmods.dev/badge/skills/thibautbaissac/rails_ai_agents/state-records.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.00083 | $0.01901 |
| Opus 5 | $0.00042 | $0.00950 |
| Sonnet 5 | $0.00017 | $0.00380 |
| Haiku 4.5 | $0.00008 | $0.00190 |
Grade A, and why
state-records 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- state-records — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Records (37signals)
State as records, not booleans. Instead of closed: boolean, create a Closure record.
Project knowledge
Tech Stack: Rails 8.2 (edge), UUIDs everywhere, ActiveRecord associations Pattern: One state model per boolean you'd normally add Naming: Noun forms (Closure, Publication, Goldness, NotNow, Archival)
Commands:
bin/rails generate model Closure card:references:uuid user:references:uuid account:references:uuid
bin/rails db:migrate
bin/rails console # Test: Card.open.count
bin/rails test test/models/
Why state records over booleans
Boolean columns give you:
- Current state (open/closed)
State records give you:
- Current state (
closure.present?) - When it changed (
closure.created_at) - Who changed it (
closure.user) - Why it changed (
closure.reason) - Change history (via events)
The pattern
Boolean approach (avoid for business state):
# BAD
class Card < ApplicationRecord
def close
update!(closed: true, closed_at: Time.current)
end
scope :open, -> { where(closed: false) }
end
State record approach:
# GOOD
class Closure < ApplicationRecord
# touch: true ensures the parent's updated_at changes when state changes,
# which drives cache invalidation (Russian doll caching, ETags, etc.)
belongs_to :card, touch: true
belongs_to :user, optional: true
belongs_to :account, default: -> { card.account }
validates :card, uniqueness: true
end
class Card < ApplicationRecord
has_one :closure, dependent: :destroy
def close(user: Current.user)
create_closure!(user: user)
end
def reopen
closure&.destroy!
end
def closed?
closure.present?
end
scope :open, -> { where.missing(:closure) }
scope :closed, -> { joins(:closure) }
end
State record model template
Every state record model follows this structure:
class Closure < ApplicationRecord
belongs_to :account, default: -> { card.account }
belongs_to :card, touch: true
belongs_to :user, optional: true
validates :card, uniqueness: true
after_create_commit :notify_watchers
after_destroy_commit :notify_watchers
private
def notify_watchers
card.notify_watchers_later
end
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.
- 9d ago First seen · 309 lines · 83 tokens per session scan A 5b7daad0d13b
state-records is a skill published in the GitHub repository ThibautBaissac/rails_ai_agents (663 stars, last pushed 3mo ago), licensed MIT. It adds 83 tokens to every session and 1,901 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-09-03.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…