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 sorah/config --skill rails-problemgit clone --depth 1 https://github.com/sorah/configWrote 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/sorah/config/rails-problem)<a href="https://agentmods.dev/skills/sorah/config/rails-problem"><img src="https://agentmods.dev/badge/skills/sorah/config/rails-problem/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/sorah/config/rails-problem"><img src="https://agentmods.dev/badge/skills/sorah/config/rails-problem.svg" alt="Reviewed on agentmods" width="80" 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.00173 | $0.02407 |
| Opus 5.5 | $0.00069 | $0.00963 |
| Sonnet 5.5 | $0.00035 | $0.00481 |
| Haiku 4.5 | $0.00017 | $0.00241 |
Grade A, and why
rails-problem 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 yesterday.
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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails API Errors with problem
Conventions for answering errors from a Rails API as RFC 9457 problem documents with the problem gem. Project-specific conventions (CLAUDE.md, docs/) always take priority.
problem works on its own: error classes declare type, status and title with its DSL, and nothing else is needed. An app whose schema lives in .proto files can instead take those from a protobuf enum through protobufable; the sections below cover both, and /sorah-guides:rails-protobuf covers the enum catalogue and answering problems over Connect RPC. Application examples come from ruby-no-kai/sponsor-app, which uses the protobuf form.
The model
An error is a class. Its type, status and title belong to the class and are declared once; only detail (and machine-readable extras) vary per occurrence. A controller concern renders every such class, and an exceptions app renders whatever escapes before a controller runs, so every failure a client sees has one shape.
- Clients dispatch on
type. A title can be reworded freely; atypeis a published identifier and is append-only. - The status is a property of the problem type, not of the code path that raised it. Two failures needing different statuses are two types.
detailis prose for a person, specific to the occurrence. Anything a client acts on goes in an extension member, never parsed out ofdetail.
Error classes
One base class carries the mixin; every error is a subclass that declares what differs. Keep them together in app/models/errors.rb (a module Errors), with a one-line doc comment per class saying when it is raised.
Plain declarations
Without protobuf, the base includes Problem::Detailable (or Problem::I18nable for translated titles, which brings Detailable with it), and each class declares its members with the DSL:
# app/models/errors.rb
module Errors
# An error the API answers as a problem.
class ApiError < StandardError
include Problem::Detailable
end
# The resource the request names does not exist.
class NotFound < ApiError
type "not-found"
status 404
title "Not Found"
end
# The resource is not in a state that allows the request.
class FailedPrecondition < ApiError
type "failed-precondition"
status 412
title "Failed Precondition"
end
end
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.
- yesterday First seen · 197 lines · 173 tokens per session scan A 249e6b86818b
rails-problem is a skill published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 173 tokens to every session and 2,407 once invoked, about $0.0007 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-10-17.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…