Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/thecodingend/rails-starternpx agentmods add skills/thecodingend/rails-starter/inertia-rails-pagesWrote 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/thecodingend/rails-starter/inertia-rails-pages)<a href="https://agentmods.dev/skills/thecodingend/rails-starter/inertia-rails-pages"><img src="https://agentmods.dev/badge/skills/thecodingend/rails-starter/inertia-rails-pages/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/thecodingend/rails-starter/inertia-rails-pages"><img src="https://agentmods.dev/badge/skills/thecodingend/rails-starter/inertia-rails-pages.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.00086 | $0.02963 |
| Opus 5 | $0.00043 | $0.01482 |
| Sonnet 5 | $0.00017 | $0.00593 |
| Haiku 4.5 | $0.00009 | $0.00296 |
Grade A, and why
inertia-rails-pages 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 10d 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.
This is a copy
100% identical to inertia-rails-pages — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inertia Rails Pages
Page components, layouts, navigation, and client-side APIs.
Before building a page, ask:
- Does this page need a layout? → Use persistent layout (React:
Page.layout = ...; Vue:defineOptions({ layout }); Svelte: module script export) — wrapping in JSX/template remounts on every navigation, losing scroll position, audio playback, and component state - Does UI state come from the URL? → Change BOTH controller (read
params, pass as prop) AND component (derive from prop, nouseState/useEffect) — userouter.getto update URL - Need to refresh data without navigation? →
router.reload({ only: [...] })— neveruseEffect+fetch - Need to update a prop without server round-trip? →
router.replaceProp— no fetch, no reload
NEVER:
- Parse
window.location.searchor useuseSearchParams— derive URL state from controller props - Use
useState/useEffectto sync URL ↔ React state — the controller passes URL-derived data as props; the component just reads them - Pass arguments to
<Deferred>render function —{(data) => ...}does NOT work; child reads viausePage() - Access
usePage().props.flash— flash is top-level:usePage().flash - Wrap layout in JSX return for persistence — use
Page.layout = ...or global layout inside createInertiaApp's resolve callback
Page Component Structure
Pages are default exports receiving controller props as function arguments.
Use type Props = { ... } (not interface — causes TS2344 in React). Vue uses defineProps<T>(), Svelte uses let { ... } = $props().
type Props = {
posts: Post[]
}
export default function Index({ posts }: Props) {
return <PostList posts={posts} />
}
Persistent Layouts
Layouts persist across navigations — no remounting, preserving scroll, audio, etc.
import { AppLayout } from '@/layouts/app-layout'
export default function Show({ course }: Props) {
return <CourseContent course={course} />
}
// Single layout
Show.layout = (page: React.ReactNode) => <AppLayout>{page}</AppLayout>
What ships with it
4 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.
- 10d ago First seen · 312 lines · 86 tokens per session scan A fab8d8dce542
inertia-rails-pages is a skill published in the GitHub repository thecodingend/rails-starter (5 stars, last pushed 9d ago), licensed MIT. It adds 86 tokens to every session and 2,963 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to inertia-rails-pages, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ui-toolkit/web
Reference skill for Zoom Video SDK UI Toolkit. Use after routing to a web video workflow when you want prebuilt React UI instead of building a fully custom Video SDK interface.
zoom-meeting-sdk-web-component-view
Zoom Meeting SDK Web - Component View. Embeddable Zoom meeting components with Promise-based API for flexible integration. Ideal for React/Vue/Angular apps and custom layouts. Uses ZoomMtgEmbedded with async/await patterns and embeddable UI containers.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
tanstack-form
Headless, performant, and type-safe form state management for TS/JS, React, Vue, Angular, Solid, Lit, and Svelte.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
web-development
Use when users need to implement, integrate, debug, build, deploy, or validate a Web frontend after the product direction is already clear, especially for React, Vue, Vite, browser flows, or CloudBase Web integration.